2009/6/10 Daryl Stultz <[email protected]> > > > Yup, I forgot the @ForeignKey annotation. I have added it and reverted to > my cascade/not deferrable setting and it seems to be working. Thanks! > > Well, the @ForeignKey did take care of the ordering of the SQL, but I deployed it to a test server and it failed the original way. I said above that I reverted to cascade/not deferrable, I did but on the wrong database instance. So I ultimately had to define the foreign key in the DB as "cascade no action deferrable initialy deferred" (PostgreSQL) to get it to work.
I have to say it's rather confusing to have an optimistic locking error thrown when the lock manager is set to none. Not sure if there is some other feedback that can be given in a case like this. -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:[email protected]
