On Wed, 23 Nov 2011, Tom Lane wrote:
In an insert command, you need to either write NULL or omit the column
from the column list; empty expressions aren't syntactically correct.
(Note that the latter option actually results in inserting the column's
default, not necessarily null...)
Tom,
I
Rich Shepard writes:
>Mine do, too. But, that's not what postgres wants to see in the .sql file.
In an insert command, you need to either write NULL or omit the column
from the column list; empty expressions aren't syntactically correct.
(Note that the latter option actually results in insert
On Wed, 23 Nov 2011, Richard Broersma wrote:
My pg.dump files show nulls as:
\N
Richard,
Mine do, too. But, that's not what postgres wants to see in the .sql file.
It takes it as a newline (\n) whether quoted or not.
Thanks,
Rich
--
Sent via pgsql-general mailing list (pgsql-general@post
On Wed, Nov 23, 2011 at 10:33 AM, Rich Shepard wrote:
> Originally I had two commas in sequence since there were no values between
> them. Next I tried a space between the two commas. I tried searching in the
> 9.0.5 manual for 'missing values', 'missing', and another term I don't
> recall but f
I am trying to load 143K rows into a postgres-9.0.5 table from an ASCII
text file. The file consists of INSERT INTO ... statements and the VALUES
are comma delimited. One column is numeric (REAL), but ~10K rows have that
value missing, and postgres rejects the lines.
The column does not have
