Re: Guarenteeing complex referencial integrity through custom triggers

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Joris Dobbelsteen <Joris(at)familiedobbelsteen(dot)nl>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Guarenteeing complex referencial integrity through custom triggers
Date: 2007-03-27 13:44:57
Message-ID: 1175003097.3701.33.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ühel kenal päeval, E, 2007-03-26 kell 16:05, kirjutas Joris Dobbelsteen:

> Oracle has choosen to allow constraint enforcement by locking on the
> parent tuple. In contrast postgres has chosen (historically, see RI
> triggers) to fail on detecting conflicting newly inserted rows (the
> cross-check).

Could you give an example, where postgresql fails to detect conflicting
newly inserted rows ?

--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-03-27 13:54:54 Re: notification payloads
Previous Message Guillaume Smet 2007-03-27 13:43:36 Partial index on varchar fields with IN