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)
just my 2cts,
grtz,
Willem
I think Node-fields can never be 'NOT NULL' because there is no way that
data-import can work then.
Especially if a Node-field is mapped to a foreign key. Because then you
cannot even fill in a 'pseudo' null value like like -1.
E.g. deploying with an empty database and cloud-context security on hsql
can now easily lead to:
at java.lang.Thread.run(Thread.java:595)java.sql.SQLException: Integrity
constraint violation - no parent MM_MMBASEUSERS_DEFAULTCONTEXT_FOREIGN
table: MM_OBJECT in statement [INSERT INTO MM_MMBASEUSERS
(M_NUMBER,OTYPE,OWNER,USERNAME,PASSWORD,DEFAULTCONTEXT,STATUS,VALIDFROM,VALIDTO,LASTLOGON)
VALUES (?,?,?,?,?,?,?,?,?,?)]
Presumable caused by the fact that an mmbaseuser is deployed before it's
default context.
I think I have proposed this earlier that a node field must always be
nullable. But in the mean time the problem remains.
Would it be possible to device another solution, and if yes how?
For the moment I'll make at least the 'defaultcontext' field of
mmbasusers nullable again, because that it the quickest solution to make
cloud-context security deploy on hsql...
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
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
