On Mon, 2008-03-17 at 01:20 -0700, Howard Chu wrote:
Andrew Bartlett wrote:
On Sat, 2008-03-15 at 18:28 +0100, Pierangelo Masarati wrote:
Pierangelo Masarati wrote:
... each instance would take care of referential integrity only within the database, but inconsistencies across databases would not be handled. I think the latter case is what you'd like to see addressed, right?
In any case it's now implemented in HEAD (ITS#5428); please test.
p.
Is the refint module synchronous or transaction based?
It is necessarily asynchronous. It will cause deadlocks in combination with other overlays if it's made synchronous. (Been there, done that, ITS's already dealt with...)
Ouch. So, is there any way I can ensure that linked attributes, possibly generated with memberOf, are always strictly consistent?
Andrew Bartlett