Re: ERROR: Bad timestamp external representation '' - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: ERROR: Bad timestamp external representation ''
Date
Msg-id Pine.LNX.4.30.0103182102440.755-100000@peter.localdomain
Whole thread Raw
In response to ERROR: Bad timestamp external representation ''  (Boris <koester@x-itec.de>)
List pgsql-general
Boris writes:

> insert into table test (...) values ('2001-03-03') works.
>
> insert into table test (...) values ('NULL') does not work,
> but in mysql it works.

That doesn't necessarily mean that MySQL is right.

> It would be great if there would be a way for 'NULL' and NULL to make
> everything more compatible.

That would certainly make everything *less* compatible.

> inserting a "NULL" in MySQL will be displayed as "NULL" and in
> postgres as "" but if you select the row with NULL it is both
> dispplayed correctly (select .. from .. where date = 'NULL' works, if
> content = "" or "NULL", thats good).

If you want to change the display of NULLs in the psql frontend, use the
\pset null command.

--
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/


pgsql-general by date:

Previous
From: jreniz
Date:
Subject: Trigger Error!
Next
From: Tom Lane
Date:
Subject: Re: ERROR: Bad timestamp external representation ''