> I think that is exactly what a relational database like Oracle does when > deferred constraint checking is enabled. true. luckily, the situation is different in jcr since we have a session and therefore can solve the "chicken and egg problem" without something like deferred constraint checking.
also, i would say that referencial integrity in jcr may be a special case, while something like a PathNotFound or a node type constraint will be taken care of up save() time. regards, david
