> Netfrastructure, incidentally, while supporting (and using, heavily)
> primary and foreign keys, does not enforce referential integrity
> for a couple of reasons. First, good programs (and Netfrastructure
> programs are good or I won't let them at it) check that stuff as
> a matter of good person hygiene, so having the system repeat the
> check is a waste of time (though admittedly cache hits).

How can good programs be responsible for reliable checking of referential
integrity (without possibility to see over transaction boundaries) ?
Or does Netfrastructure support dirty reads ? :-)

Ivan