Re: ERROR: Bad timestamp external representation ''

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Boris <koester(at)x-itec(dot)de>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: Bad timestamp external representation ''
Date: 2001-03-18 20:05:16
Message-ID: Pine.LNX.4.30.0103182102440.755-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Eric G. Miller 2001-03-18 20:14:19 Re: ERROR: Bad timestamp external representation ''
Previous Message Tom Lane 2001-03-18 19:30:11 Re: ERROR: Bad timestamp external representation ''