On 10/7/14, 10:40 PM, Gavin Flower wrote:
Yeah, I'm pretty convinced at this point that history/versioning should be
built on top of a schema that always contains the current information, if for
no other reason than so you always have a PK that points to what's current in
addition to your
On 10/6/14, 6:10 PM, Gavin Flower wrote:
Even if timestamps are used extensively, you'd have to be careful joining on them.
You may have information valid at T1 and changing at T3, but the transaction has T2,
where T1 T2 T3 - the appropriate set of data would be associated with T1,
would
On 08/10/14 13:29, Jim Nasby wrote:
On 10/6/14, 6:10 PM, Gavin Flower wrote:
Even if timestamps are used extensively, you'd have to be careful
joining on them. You may have information valid at T1 and changing at
T3, but the transaction has T2, where T1 T2 T3 - the appropriate
set of data
On 10/2/14, 9:27 AM, Adam Brusselback wrote:
i've also tried to implement a database versioning using JSON to log changes in
tables. Here it is:
https://github.com/fxku/audit[https://github.com/fxku/audit][https://github.com/fxku/audit[https://github.com/fxku/audit]]
On 07/10/14 10:47, Jim Nasby wrote:
On 10/2/14, 9:27 AM, Adam Brusselback wrote:
i've also tried to implement a database versioning using JSON to log
changes in tables. Here it is:
...@gmx.de
*Cc:* pgsql-general@postgresql.org pgsql-general@postgresql.org
*Betreff:* Re: [GENERAL] table versioning approach (not auditing)
I know we're kinda hijacking this thread, so sorry for that. If you'd
like to do that, i'd be more than happy to use it and push any fixes /
changes
for that.
Cheers
Felix
*Gesendet:* Mittwoch, 01. Oktober 2014 um 17:09 Uhr
*Von:* Adam Brusselback adambrusselb...@gmail.com
*An:* Felix Kunde felix-ku...@gmx.de
*Cc:* pgsql-general@postgresql.org pgsql-general@postgresql.org
*Betreff:* Re: [GENERAL] table versioning approach (not auditing
Brusselback adambrusselb...@gmail.com
An: Felix Kunde felix-ku...@gmx.de
Cc: pgsql-general@postgresql.org pgsql-general@postgresql.org
Betreff: Re: [GENERAL] table versioning approach (not auditing)
Felix, I'd love to see a single, well maintained project. For example, I just
found yours
abelardhoff...@gmail.com[abelardhoff...@gmail.com
]
An: pgsql-general@postgresql.org[pgsql-general@postgresql.org]
pgsql-general@postgresql.org[pgsql-general@postgresql.org]
Betreff: [GENERAL] table versioning approach (not auditing)
Hi. I need to maintain a record of all changes to certain tables
: Abelard Hoffman abelardhoff...@gmail.com
An: Felix Kunde felix-ku...@gmx.de
Cc: pgsql-general@postgresql.org pgsql-general@postgresql.org
Betreff: Re: [GENERAL] table versioning approach (not auditing)
Thank you Felix, Gavin, and Jonathan for your responses.
Felix Jonathan: both of you mention just
...@gmail.com
An: Felix Kunde felix-ku...@gmx.de
Cc: pgsql-general@postgresql.org pgsql-general@postgresql.org
Betreff: Re: [GENERAL] table versioning approach (not auditing)
Thank you Felix, Gavin, and Jonathan for your responses.
Felix Jonathan: both of you mention just storing deltas. But if you
Hoffman abelardhoff...@gmail.com
An: pgsql-general@postgresql.org pgsql-general@postgresql.org
Betreff: [GENERAL] table versioning approach (not auditing)
Hi. I need to maintain a record of all changes to certain tables so assist in
viewing history and reverting changes when necessary (customer
In the past, to accomplish the same thing I've done this:
- store the data in hstore/json. instead of storing snapshots, I store deltas.
i've been using a second table though, because it's improved performance on
reads and writes.
- use a transaction log. every write session gets logged
On September 29, 2014 11:08:55 AM EDT, Jonathan Vanasco postg...@2xlp.com
wrote:
- use a transaction log. every write session gets logged into the
transaction table (serial, timestamp, user_id). all updates to the
recorded tables include the transaction's serial. then there is a
the affected records.
Have a look and tell me what you think of it.
Cheers
Felix
Gesendet: Montag, 29. September 2014 um 04:00 Uhr
Von: Abelard Hoffman abelardhoff...@gmail.com
An: pgsql-general@postgresql.org pgsql-general@postgresql.org
Betreff: [GENERAL] table versioning approach
On Sep 29, 2014, at 4:06 PM, Nick Guenther wrote:
A newbie tangent question: how do you access the transaction serial? Is it
txid_current() as listed in
http://www.postgresql.org/docs/9.3/static/functions-info.html?
My implementations were ridiculously simple/naive in design, and existed
Hi. I need to maintain a record of all changes to certain tables so assist
in viewing history and reverting changes when necessary (customer service
makes an incorrect edit, etc.).
I have studied these two audit trigger examples:
https://wiki.postgresql.org/wiki/Audit_trigger
On 29/09/14 15:00, Abelard Hoffman wrote:
Hi. I need to maintain a record of all changes to certain tables so
assist in viewing history and reverting changes when necessary
(customer service makes an incorrect edit, etc.).
I have studied these two audit trigger examples:
18 matches
Mail list logo
