Willem Voogd wrote: > It's been a while since i posted anything to this list, so hereby some > proof of my ongoing existence... :) > > 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? > > That way the constraint on DB level can be kept intact and also when > applied when the import is done, it is an extra check to whether the import > succeeded (respecting all constraints as a post condition)
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'. I tende to agree with gomez that we can utilize the distincion (existing since last week) between 'required' and 'not null'. MIchiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
