From: | Les <nagylzs(at)gmail(dot)com> |
---|---|
To: | Lorusso Domenico <domenico(dot)l76(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: foreign keys on multiple parent table |
Date: | 2023-06-20 21:01:32 |
Message-ID: | CAKXe9UBzzh0CK9MWRHTWVLBmoKCji18PiOA1ZnnPJtn1bquWUg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> .
>
> From programming point of view and also to reduce the number of objects in
> DB could be convinient create just an audit table with a structure like:
>
> - auditi id
> - reference_uuid (the key of the main table)
> - table_name
> - list of audit data
>
>
Could work, but is there a way to set a reference key over the uuid of all
> the tables?
>
For existing solution, check out
https://github.com/2ndQuadrant/audit-trigger
Regarding fk constraints, a single fk constraint can only reference the
primary key of a single table.
But, if you want to be serious about audit logs, then you need to keep logs
of deletions too, and for those, foreign key constraints would not work
anyway.
You may also want to consider bulk insert speed. Foreign key constraint
checking can reduce speed.
Laszlo
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2023-06-20 21:19:07 | Re: pb with join plan |
Previous Message | David G. Johnston | 2023-06-20 20:50:48 | Re: foreign keys on multiple parent table |