Re: FW: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
От | Stephan Szabo |
---|---|
Тема | Re: FW: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 |
Дата | |
Msg-id | 20030819232729.P91704-100000@megazone.bigpanda.com обсуждение исходный текст |
Ответ на | FW: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 -13' (Arnold Mavromatis <A.Mavromatis@bom.gov.au>) |
Список | pgsql-bugs |
On Wed, 20 Aug 2003, Arnold Mavromatis wrote: > db1=> select * from sfc_days2 where lsd = to_date('1901-12-13', > 'YYYY-MM-DD'); > stn_num | lsd | max_air_temp > ---------+------------+-------------- > 86071 | 1901-12-13 | 3.0 > (1 row) > > db1=> select * from sfc_days2 where lsd = to_date('1901-12-14', > 'YYYY-MM-DD'); > stn_num | lsd | max_air_temp > ---------+------------+-------------- > 86071 | 1901-12-13 | 3.0 > (1 row) I don't have a particularly good idea of why that would be happening, but does select (date '1901/12/13' = date '1901/12/14'); return true for you (attempting to see if you get the same results from a different method of getting the date fields). And what does select timestamp '1901/12/13' + interval '1 day'; give you? > As for compiler options I believe everything was left as default for HP-UX > 11.11 (Ie the options that you have recommended I do not know if they were > set...) without further investigation... Actually it looks like the option I was remembering that broke some of the datetime functionality is at least checked for explicitly in 7.3.4 and gives a compile time error.
В списке pgsql-bugs по дате отправления: