|Re: false but not true [message #522526 is a reply to message #522502]
||Mon, 22 March 2010 17:02
| Tom Eugelink
Registered: July 2009
> What was the delivered to begin with? If it was already true, then|
> setting it to true will have no effect, so nothing will be written to
> the database.
It's being toggled. The resulting boolean also means another record is either inserted or deleted, and that record is correctly handled (so when false -> true the record is correctly inserted, when true -> false it is correctly removed).
But once the entity's property is set to false, it stays false. In memory it is set to true, the related record is inserted, but the entity itself is simply not persisted.
Same goes for a text property I update synchronous to the boolean (always append an "x"). When the entity goes from true -> false the text field also is updated, from false -> true it isn't. The EM seems to ignore it.
If I create a small test scenario, it works as expected. So it some circumstantial factor.
Powered by FUDForum
. Page generated in 0.03639 seconds