Re: Time zone offset in to_char()
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Alban Hertroijs <a.hertroijs@nieuwestroom.nl>,
Karsten Hilbert <Karsten.Hilbert@gmx.net>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2024-01-11T17:27:37Z
Lists: 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