| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | wsheldah(at)lexmark(dot)com |
| Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org>, General Postgres List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: date/time formats in 7.2 |
| Date: | 2001-12-31 20:45:13 |
| Message-ID: | 3C30CE59.A4CDFD7D@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> The one variant I'd like it to accept is 'yyyy-mm-ddThh:nn:ss', as in
> '2001-12-31T13:30:46'. This is the ISO-8601 format that perl's Time::Piece and I
> think at least one other perl date module use as their 'standard ISO' output
> format, and the default format that's closest to what Postgresql 7.1.3 seems to
> accept. For now, I'm taking a string that looks like the above, replacing the T
> with a space with Perl, and then inserting the value into Postgresql. Not a huge
> deal, of course, but it might make it a little more convenient for some of us.
Already accomodated in 7.2.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael McAlpine | 2001-12-31 21:08:43 | Large Tables/clustering/terrible performance of Postgresql |
| Previous Message | Serguei Mokhov | 2001-12-31 19:36:05 | [OT] Happy New Year tout le monde! |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Olivier PRENANT | 2001-12-31 22:23:11 | Happy new year |
| Previous Message | Thomas Lockhart | 2001-12-31 20:43:23 | Re: Latest datetime changes produce gcc complaints |