PG not rejecting bad dates (was Re: Finding bogus dates)

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: PG not rejecting bad dates (was Re: Finding bogus dates)
Date: 2007-01-18 23:42:54
Message-ID: 45B005FE.4010308@cox.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/18/07 17:22, Scott Ribe wrote:
>> But this won't work if one had a text column of dates in various
>> formats, right?
>
> Right. In my case I have bad data from a source I didn't control, exported
> via code that I do control which happens to output YYYY-MM-DD. Well, except
> that I don't do what I need to when MM or DD are more than 2 digits, but I'm
> going back to look at that again ;-)

Why didn't the PG engine reject these bad-date records at INSERT
time. This smacks of something that MySQL would do...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFsAX+S9HxQb37XmcRAg9NAJ4mdQXdp0tLDpiLcTaOVVrZgUMdSACgjTti
9iVMxYAWNIKOwtfm3T38Aac=
=Rpbe
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-01-18 23:43:42 Re: drive failre, corrupt data...
Previous Message Scott Ribe 2007-01-18 23:22:39 Re: Finding bogus dates