copy the contents of a file into a table column. First load the file into a
variable and then proceed as above.
-testdb=> \set content '\'' `cat my_file.txt` '\''
+testdb=> \set content '''' `cat my_file.txt` ''''
testdb=> INSERT INTO my_table VALUES (:content);
One possible problem with this approach is that my_file.txt
they don't cause a syntax error when the second line is processed. This
could be done with the program sed:
-testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\''
+testdb=> \set content '''' `sed -e "s/'/\\\\''/g" < my_file.txt` ''''
Observe the correct number of backslashes (6)! It works
this way: After
psql has parsed this
- line, it passes sed -e "s/'/\\\'/g" < my_file.txt
+ line, it passes sed -e "s/'/\\''/g" < my_file.txt
to the shell. The shell will do its own thing inside the double
quotes and execute sed with the arguments
- -e and s/'/\\'/g. When
+ -e and s/'/''/g. When
sed parses this it will replace the two
backslashes with a single one and then do the substitution. Perhaps
at one point you thought it was great that all Unix commands use the
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/bin/psql/psqlscan.l,v 1.18 2006/05/11 19:15:35 tgl Exp $
+ * $PostgreSQL: pgsql/src/bin/psql/psqlscan.l,v 1.19 2006/05/31 11:35:17 momjian Exp $
*
*-------------------------------------------------------------------------
*/
{quote} { return LEXRES_OK; }
+ /* We don't need a state here because we are already in a string */
+{xqdouble} { emit("'", 1); }
+
"\\n" { appendPQExpBufferChar(output_buf, '\n'); }
"\\t" { appendPQExpBufferChar(output_buf, '\t'); }
"\\b" { appendPQExpBufferChar(output_buf, '\b'); }