Michiel Meeuwissen wrote:
Willem Voogd wrote:
Maybe this is thought of already and dismissed, but isn't a simpler
option
to have the respective constraints (not null and foreign key reference)
disabled during import?
It seems cumbersome to apply and unapply database-constraints before and
after importing. Especially since AFAIK even applying such constraints
is as yet not available 'atomicly'.
Ah, true, didnt think of that...
I tende to agree with gomez that we can utilize the distincion (existing
since last week) between 'required' and 'not null'.
True, although it takes responsibilty from the storage layer, so possible
3rd party (non MMBase apps) accessing your DB won't get checked. But when
one 'stays inside' MMBase, it'll still respect the 'check your borders, then
inside your system your data will be consistent' principle...
Willem
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
