From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Date Representation Bug. Timezone and update on an already posted as #208 reportbug |
Date: | 2001-04-20 13:01:10 |
Message-ID: | 200104201301.f3KD1Af57957@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Gianfranco Pesce (g(dot)pesce(at)hotbrain(dot)it) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Date Representation Bug. Timezone and update on an already posted as #208 reportbug
Long Description
The problem of date representation of 22/05/1977 and 28/05/1978 is
related with time zone.
The system is a Linux RedHat 6.2 (also tested on Redhat 7.0 and 7.1) with postegresql 6.5 and 7.1.
ONLY 22/05/1977 and 28/05/1978 are bad recorded into the db. This dates are stored (or retrieved) as 21/05/1977 ans 27/05/1978 respectively. ALL other date correcly stored.
If I modify my timezone from MET (DayLight Saving Time Enabled) to PDT
the bug disappears.
Sample Code
echo $PGDATESTYLE
SQL,EUROPEAN
test=> create table pippo (d date);
CREATE
test=> insert into pippo values ('22/05/1977');
INSERT 629024 1
test=> insert into pippo values ('28/05/1978');
INSERT 629025 1
test=> insert into pippo values ('30/10/1964');
INSERT 629026 1
test=> select * from pippo;
d
------------
21/05/1977
27/05/1978
30/10/1964
(3 rows)
test=> select * from pippo where d = '22/05/1977';
d
------------
21/05/1977
(1 rows)
No file was uploaded with this report
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-04-20 14:46:36 | Re: Date Representation Bug. Timezone and update on an already posted as #208 reportbug |
Previous Message | Peter T Mount | 2001-04-20 11:12:36 | Re: 7.0.3 dumps aren't accessible via JDBC in 7.1 |