| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | Michal Kalanski <kalanskim(at)zetokatowice(dot)pl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dates in inserts |
| Date: | 2003-04-01 15:42:45 |
| Message-ID: | 961.1049211765@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> Probably becuase there is no 13th month so 01.13.03 can only be
> interpreted as the 13th of January.
Right, and the same goes for 13.01.03: even if your datestyle is mmddyy,
the date parser will take this as ddmmyy, because otherwise it couldn't
be valid. AFAIK there is no way to force the date parser to reject the
input instead. Datestyle is used to drive the interpretation when the
input is ambiguous, but not when there is only one interpretation that
will work.
If you prefer to be stiff-necked then I'd recommend putting some
validation on the client side.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ps | 2003-04-01 15:47:14 | bug in deferred triggers ? |
| Previous Message | Bruno Wolff III | 2003-04-01 15:35:06 | Re: stored procedure |