| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
| Cc: | "Derek Rodner" <derek(dot)rodner(at)enterprisedb(dot)com>, pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: Oracle, MySQL, and PostgreSQL feature comparison - Part 2 |
| Date: | 2007-10-11 18:53:04 |
| Message-ID: | 36e682920710111153y74215a1hcf1a280863c019a8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 10/11/07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> Postgresql too has this functionality and it seems to be as flexible and
> configurable as Oracle's.
Not exactly. Oracle auditing uses autonomous transactions and
actually logs attempts to change data as well as changes themselves
whereas Postgres would only log to a table on commit. In Postgres,
you have to specifically write a trigger which simulates an autonomous
transaction using dblink.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2007-10-11 19:01:36 | Re: Oracle, MySQL, and PostgreSQL feature comparison - Part 2 |
| Previous Message | Christian Voelker | 2007-10-11 18:49:16 | Re: Oracle, MySQL, and PostgreSQL feature comparison - Part 2 |