From: | Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> |
---|---|
To: | "pgsql-general (at) postgresql (dot) org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: A creepy story about dates. How to prevent it? |
Date: | 2003-06-18 23:09:26 |
Message-ID: | 20030619000926.A19922@bacon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 18/06/2003 22:09 scott.marlowe wrote:
> [snip]
> Why bother checking for wrong dates sometimes (i.e. 03/33/2003) but not
> all the time (i.e. 13/03/2003)?
ISTR that DB2 used to do the same (maybe still does - haven't used it for
a few years). Still, IMHO, it is frustrating. I would rather have the db
be ultra-strict, forcing me to handle dates correctly and rigorously in my
app.
> [snip]
> I do plenty of format checking, this isn't the same. This is range
> checking. I expect my database to do that for me.
Agreed, although if the user gets his data thrown back at him by the db
then I feel that this is a bug in my program. YMMV.
regards
--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants |
http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Jacobs | 2003-06-19 01:28:26 | PlPython |
Previous Message | Andrew Snow | 2003-06-18 22:38:52 | Re: A creepy story about dates. How to prevent it? |