[Bug 679] Problems with persist() and collections using accessName

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown [Bug 679] Problems with persist() and collections using accessName

by Bugzilla from bugzilla-daemon@helma.at :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://dev.helma.org/bugs/show_bug.cgi?id=679





--- Comment #3 from tobi <interface@...>  2009-10-07 17:26:03 ---
Created an attachment (id=123)
 --> (http://dev.helma.org/bugs/attachment.cgi?id=123)
Test app to demonstrate the bug

If you call Root.main_action() of the test app you should see a debug output
like "null" which is the result of retrieving an object by the name "test".

Nevertheless, the action always creates a new object with that name and if you
look into the database you will see that one record after another is added.

Thus, I suspect the collection root.bar.foos is not updated correctly.

After a restart of the app everything is as it should be (you will get the
object’s string represenation in the debug message) -- except that you might
find yourself in the delicate situation of having a bunch of objects with the
same access name in the database.

--
Configure bugmail: http://dev.helma.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev