*I removed the first row (column labels) and replaced all of the ''tabs'' with commas; I also turned the extra commas into null values: <code>cat Product.txt | sed "1D" | sed "s/\t/,/g" | sed "s/,,/,null,/g"</code>

*I removed the first row (column labels) and replaced all of the ''tabs'' with commas; I also turned the extra commas into null values: <code>cat Product.txt | sed "1D" | sed "s/\t/,/g" | sed "s/,,/,null,/g"</code>

*I began placing the apostrophes around the ''varchar'' data with the ''Form'', ''Dosage'', and ''TECode'' data. I placed apostrophes around this data by adding several <code>sed</code> replacements to the pipeline made earlier: <code>sed "s/,/&'/2" | sed "s/,/'&/3" | sed "s/,/&'/3" | sed "s/,/'&/4" | sed "s/,/&'/5" | sed "s/,/'&/6"</code>

*I began placing the apostrophes around the ''varchar'' data with the ''Form'', ''Dosage'', and ''TECode'' data. I placed apostrophes around this data by adding several <code>sed</code> replacements to the pipeline made earlier: <code>sed "s/,/&'/2" | sed "s/,/'&/3" | sed "s/,/&'/3" | sed "s/,/'&/4" | sed "s/,/&'/5" | sed "s/,/'&/6"</code>

*I noticed that there are a few commas and apostrophes in the raw data, I decided to initially replace the commas with characters that are not present elsewhere in the raw data (such as''~''); <code>sed "s/,/~/g"</code> was added to the beginning of the command chain to initially replace them, and <code>sed "s/~/,/g"</code> was added to the end of chain in order to restore them. The presence of apostrophes in the data was fixed by through adding <code>sed "s/'/''/g"</code> to the beginning of the pipe (this addition allows pgSQL to understand that these apostrophes are a part of the actual data.

*I noticed that there are a few commas and apostrophes in the raw data, I decided to initially replace the commas with characters that are not present elsewhere in the raw data (such as''~''); <code>sed "s/,/~/g"</code> was added to the beginning of the command chain to initially replace them, and <code>sed "s/~/,/g"</code> was added to the end of chain in order to restore them. The presence of apostrophes in the data was fixed by through adding <code><nowiki>sed "s/'/''/g"</nowiki></code> to the beginning of the pipe (this addition allows pgSQL to understand that these apostrophes are a part of the actual data.

*I placed apostrophes around all remaining ''varchar'' data by adding <code>sed "s/,/&'/7" | sed "s/,/'&/8" | sed "s/,/&'/8" | sed "s/\r$/'/g"</code> to the pipeline

*I placed apostrophes around all remaining ''varchar'' data by adding <code>sed "s/,/&'/7" | sed "s/,/'&/8" | sed "s/,/&'/8" | sed "s/\r$/'/g"</code> to the pipeline

*To the end of the current pipeline, I added <code>sed "s/^/insert into products(ApplNo,ProductNo,Form,Dosage,ProductMktStatus,TECode,ReferenceDrug,drugname,activeingred) values(/g" | sed "s/$/);/g"</code> to wrap up the formatting of the raw data (should now be usable as sequences of SQL <code>insert</code> statements)

*To the end of the current pipeline, I added <code>sed "s/^/insert into products(ApplNo,ProductNo,Form,Dosage,ProductMktStatus,TECode,ReferenceDrug,drugname,activeingred) values(/g" | sed "s/$/);/g"</code> to wrap up the formatting of the raw data (should now be usable as sequences of SQL <code>insert</code> statements)