| From: | Michael Fuhr <mike(at)fuhr(dot)org> | 
|---|---|
| To: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: postgresql vs mysql | 
| Date: | 2007-02-21 14:42:26 | 
| Message-ID: | 20070221144226.GA94033@winnie.fuhr.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-21 14:44:43 | Re: Slow running to_tsvector (tsearch2 in PG 8.2.3) | 
| Previous Message | Tom Lane | 2007-02-21 14:35:47 | Re: Odd behaviour of timestamptz |