| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Monica kroger <webmaster(at)rocky(dot)edu> |
| Cc: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
| Subject: | Re: [PORTS] Port Bug Report: Error with date_part when checking month |
| Date: | 1999-03-03 15:28:10 |
| Message-ID: | 36DD550A.18F9D18A@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-ports |
> eventstart|date_part
> ----------+---------
> 06-15-1999| 6
> The data was entered in this same time zone. It was entered as
> 'mm-dd-yyyy' from a PHP3 form using a standard SQL insert.
Ah, it is the date data type. I now recall that I fixed some time zone
conversion problems in this data type. Postgres v6.4.2, plus some
patches on the web site, will fix this problem, which was first
identified at the end of December. The upcoming v6.4.3 will have the
fixes already applied.
If you don't want to install and patch a new version of Postgres, try
using the datetime data type instead.
Sorry for the problems...
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 1999-03-03 15:44:18 | Re: [HACKERS] palloc.h again |
| Previous Message | Tom Lane | 1999-03-03 15:14:48 | Re: [HACKERS] palloc.h again |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Unprivileged user | 1999-03-03 19:26:35 | Port Bug Report: destroydb fails with ERROR: typeidTypeRelid: Invalid type - oid = 0 |
| Previous Message | Thomas G. Lockhart | 1999-03-03 04:52:37 | Re: [PORTS] Port Bug Report: Can not create table with a number as first character |