Mapping is biggest weakness in o/r mapping right now =(
Most issues come down to "not quite correct" mapping all too often =(
On Aug 10, 2005, at 11:22 AM, Guillaume Laforge wrote:
Hi again,
I hesitate to reveal the truth and expose how stupid I must be... but
still... I think I've found the source of my problem. It seems as if
it were a mere mapping issue!
What a pity the messages are so misleading... I guess some sanity
checker is in order so that we can compare a mapping and a database's
schema (hint, hint Brian!).
In my mapping, it seems like I had configured a many-to-many
relationship, though what I really had was a simple one-to-many
relationship: I had a foreignkey AND remote-foreignkey in my xdoclet
tags pointing at the same column. Though obviously the
remote-foreignkey wasn't needed at all.
Then, I set back autocommit to 2 explicitely (to be sure I was in
autocommit false), and tried again my little test... and... tada...
all my objects were rollbacked as I expected!
I'm sad I wasted that many hours on such a trivial problem :-(
I apologize for having bothered you with somewhat of a false
problem :-(
Anyway, thanks a lot for your great support and help.
--
Guillaume Laforge
http://glaforge.free.fr/blog/groovy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
