Re: Time zone offset in to_char()
| От | Adrian Klaver |
|---|---|
| Тема | Re: Time zone offset in to_char() |
| Дата | |
| Msg-id | 5fb4d1a8-0597-4f87-9a6b-db1a99b0ebfe@aklaver.com обсуждение исходный текст |
| Ответ на | Re: Time zone offset in to_char() (Adrian Klaver <adrian.klaver@aklaver.com>) |
| Ответы |
Re: Time zone offset in to_char()
|
| Список | pgsql-general |
On 1/11/24 08:48, Adrian Klaver wrote: > On 1/11/24 08:04, Alban Hertroijs wrote: >> The drawback, as mentioned, being that we need to maintain those >> functions in each deployment, which is a bit of a hassle (albeit a >> minor one) because we need to customise both the TDV side and the >> PostgreSQL side in that case. Our preferred solution would be to just >> add a few entries to the TDV database-specific capabilities file (as >> described in my initial message) > > Are you referring to?: > > "It currently have this: > ToDatetimeOffsetNL(~any) : ciscache.ToDatetimeOffsetNL($1) > ToDatetimeOffset(~any,~any) : ciscache.ToDatetimeOffset($1, $2) > " It finally dawned on me, you want to replace the user defined functions above with Postgres builtins only. Try as I might I could not come with that solution. > > I thought the issue there was maintaining the two Postgres functions? > > >> Provided that such a solution is possible, that is. If not, my current >> approach may have to suffice. >> >> The reason I decided to ask on the ML is that I'm finding it hard to >> believe that this transformation would be this difficult, so I expect >> that I must be missing something. >> >> Regards, >> Alban Hertroys > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: