On 6/17/21 11:10 PM, David G. Johnston wrote:
And, since its not in the commitfest app, and the last emails I found
are over a year old, it doesn’t seem to be a priority for anyone at this
time.
I'm working on the application-time (aka valid-time) side of this, and
there is another patch for
Hi,
Am 18.06.2021 um 09:15 schrieb goldgraeber-werbetech...@t-online.de:
Hi,
I just cannot see what is wrong with my query:
create table files (id int, name text, prev_name text, );
create table fnchanged (id int, name text);
update files f set prev_name = f.name, name = c.name from
Hi,
I just cannot see what is wrong with my query:
create table files (id int, name text, prev_name text, );
create table fnchanged (id int, name text);
update files f set prev_name = f.name, name = c.name from fnchanges c where
f.id = c.id and c.name != f.name
--- gets syntax error at
On Fri, 2021-06-18 at 10:28 +1000, Gavan Schneider wrote:
> On 18 Jun 2021, at 9:34, David G. Johnston wrote:
> > On Thursday, June 17, 2021, Gavan Schneider
> > wrote:
> >
> > > My approach is to define such fields as ‘text’ and set a constraint using
> > > char_length(). This allows PG to do
On Thursday, June 17, 2021, Anand Sowmithiran wrote:
> I am looking to use the temporal tables feature for keeping track of
> changes to my table data. As of now, there is an pgxn.org provided
> extension by which we could leverage this functionality, but *when
> Temporal tables will become part
