Hi, thanks for elaborating. yes, of course, I can implement it with 3 triggers, adding a couple of columns. It doesn't affect design and testing which stay the same. As we are developing a product that must support a couple of databases and as I am not really happy with Maria e.a., I want to switch our standard DBMS. We need to support ms and ora as well, so there are h2, db2 and pg, or maybe we switch to some nonrel stuff like neo. A couple of years ago I migrated a cms from db2 to pg, and was quite impressed... thats my current "mind map" :-)
Von meinem iPhone gesendet > Am 10.11.2016 um 01:26 schrieb Craig Ringer <craig.rin...@2ndquadrant.com>: > > On 8 Nov. 2016 15:11, "Craig Ringer" <cr...@2ndquadrant.com> wrote: > > > > > > > > On 7 November 2016 at 05:08, Stefan Scheid <s...@4braincells.de> wrote: > >> > >> Hi all, > >> > >> are there plans to introduce temporal tables? > > > > I don't know of anybody working on them, but someone else may. Try > > searching the list archives. > > I should've mentioned that one of the reasons it doesn't seem to be that high > on many people's priority lists is that it's fairly easy to implement with > triggers and updatable views. There's a greater performance cost than I'd > expect to pay for the same thing done as a built-in feature, but it works > well enough. > > Many ORMs and application frameworks also offer similar capabilities at the > application level. > > So I think temporal tables are one of those nice-to-haves that so far people > just find other ways of doing.