Re: postgresql vs mysql - Mailing list pgsql-general

From Michael Fuhr
Subject Re: postgresql vs mysql
Date
Msg-id 20070221144226.GA94033@winnie.fuhr.org
Whole thread Raw
In response to Re: postgresql vs mysql  (Jan de Visser <jdevisser@digitalfairway.com>)
Responses Re: postgresql vs mysql  (Ron Johnson <ron.l.johnson@cox.net>)
List pgsql-general
On Wed, Feb 21, 2007 at 08:54:30AM -0500, Jan de Visser wrote:
> It gets better: The problem is not just feb 35, it's also that it doesn't warn
> you that it didn't like the input format:

Actually it did, sort of.

> mysql> insert into test values ('35-Feb-2007');
> Query OK, 1 row affected, 1 warning (0.07 sec)
                            ^^^^^^^^^
mysql> show warnings;
+---------+------+-----------------------------------------+
| Level   | Code | Message                                 |
+---------+------+-----------------------------------------+
| Warning | 1265 | Data truncated for column 'td' at row 1 |
+---------+------+-----------------------------------------+
1 row in set (0.00 sec)

Not as good as "ERROR: hey bonehead, there ain't no such date" but
at least it's something :-)

--
Michael Fuhr

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Odd behaviour of timestamptz
Next
From: Tom Lane
Date:
Subject: Re: Slow running to_tsvector (tsearch2 in PG 8.2.3)