Hallo Ute,
beeing a little late for the discussion I hope you could solve your
problem already. In case not I have a suspicion regarding your second
problem as I stumbled over the same error message recently.
My problem appeared as I tried to delete an object which has "relations"
to no longer existing objects or rather there were foreign keys left
which did no longer represent any valid object. So EOF replaces that
with "fake"-eos (instead of throwing an error immediatly). The error
message was caused by a modeled to-many back relationship which should
have been set to null according deletion rule. So EOF tried to set this
to-may-relation in the fake eo which throws the error.
So my advice would be to check your data integrity. To find such "fake"
eos Chuck has a method suggested in his book (Chapter 3, section
"Detecting Referential Integrity Problems") which was very helpful to me.
Regards
Susanne
--
Susanne Schneider
Coordinator secuSuite Development
iAS interActive Systems GmbH
Dieffenbachstraße 33 c, D-10967 Berlin
fon +49(0)30 69 00 42 - 05
fax +49(0)30 69 00 42 - 10
mail [EMAIL PROTECTED]
web http://www.interActive-Systems.de
----------------------------------------------------
Geschäftsführer: Dr. Marko Reschke, Thomas Fritzsche
Sitz der Gesellschaft: Berlin
Amtsgericht Berlin Charlottenburg, HRB 106103B
----------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
