Re: Dates in inserts
От | scott.marlowe |
---|---|
Тема | Re: Dates in inserts |
Дата | |
Msg-id | Pine.LNX.4.33.0304011026040.13402-100000@css120.ihs.com обсуждение исходный текст |
Ответ на | Re: Dates in inserts (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Dates in inserts
|
Список | pgsql-general |
On Tue, 1 Apr 2003, Tom Lane wrote: > "Nigel J. Andrews" <nandrews@investsystems.co.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. I think the better answer is to only insert dates in an unambiguous format.
В списке pgsql-general по дате отправления: