Has anyone had problems updating data managed read-only collections? Here are two different scenarios that are causing us problems.

We have an Object1 that has a one-to-many/many-to-one bi-directional "read-only" collection of Object2's.

Method 1:
We create a new Object2 and add the reference to Object1 to this object
We then commit Object2 using dataService.commit([Object2])
We handle the result of that commit and then add Object2 to the collection in Object1
We then commit Object1

Problem... when we use this method, the Object1 id appears in the Object2 table after the commit of Object2, however then in the next commit of Object1, it gets changed to NULL.


Method 2:
We create a new Object2 and add the reference to Object1 to this object
We then add Object2 to the collection in Object1
We then commit Object1

Problem... when we use this method, the commit of Object1 takes an extraordinarily long time. It also hangs the browser as if the Flash Player is being pushed to it's limit. Our Object2 collections have only 2-3 items in them and there are only about 250 Object1's in the database so it's not like we are dealing with huge amounts of data at this point.

Any thought or ideas about this would really help us. We are completely stuck at this point since neither method produces any error messages.

Thanks!

Kevin

Reply via email to