Re: RFC 9557 / IXDTF
| От | Adrian Klaver |
|---|---|
| Тема | Re: RFC 9557 / IXDTF |
| Дата | |
| Msg-id | 72d49ca8-535e-4ab9-8156-6cdc43d8942b@aklaver.com обсуждение исходный текст |
| Ответ на | RFC 9557 / IXDTF (pgmis@posteo.net) |
| Список | pgsql-general |
On 11/16/25 11:43, pgmis@posteo.net wrote: > Hello, > > does postgres consider some sort of implementation of rfc9557 IXDTF? > This is new time internet time format which extends timestamps with > timezone info together with the offset > - https://datatracker.ietf.org/doc/html/rfc9557 > - https://en.wikipedia.org/wiki/RFC_9557#Usage > > If not, is there some suggestion on how to best store information like > this? select '1996-12-19T16:39:57-08:00[America/Los_Angeles]'::timestamp; ERROR: invalid input syntax for type timestamp: "1996-12-19T16:39:57-08:00[America/Los_Angeles]" select '1996-12-19T16:39:57-08:00[America/Los_Angeles]'::timestamptz; ERROR: invalid input syntax for type timestamp with time zone: "1996-12-19T16:39:57-08:00[America/Los_Angeles]" select '1996-12-19T16:39:57-08:00[America/Los_Angeles]'::varchar; varchar ------------------------------------------------ 1996-12-19T16:39:57-08:00[America/Los_Angeles] Your only option at this point would be to store as a string. That means though you lose out on using any of the Postgres datetime operators or functions, unless you do some regex to pull out the timezone portion and then use that with the datetime string to create a timestamp or timestamptz. I could see that being wrapped into a function. > > Thanks, > Miroslav > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: