DatabaseErrorException – ReadOnlyEntityUpdate

[Florian Rothenaicher]

We are getting more and more “Firefly.Box.Data.DataProvider.DatabaseErrorException – ReadOnlyEntityUpdate” errors in our application.

 

In the task where the error is triggered or logged, the entity has the “ReadOnly” property set to "true". The task defenitly only checks data, so no write operation or “OnSaving” should be triggered.

In previous tasks, the entity may already have been opened for writing.

Is the write mode (Readonly) set by the parent tasks and inherited by the child tasks?

We had hoped that disabling the “ShouldDetermineNameAccordingToCallStack” setting would be a solution to our problem. But it is already set to “False.”

One more note: We have an OnSaving handler in the affected entity.

In this handler changes are made to columns. We assume that OnSaving is only triggered when a record has been modified in a controller and needs to be written to the database.

A major problem is that the errors cannot be reproduced. If I perform the same operation again, the error does not occur.

Has anyone else experienced similar problems or have any suggestions on how we can narrow down the cause?

[Noam Honig]

Hi Florian,

I'm not aware of any misbehaviors of ReadOnlyEntityUpdate - if I were in your shoes and wanted to track it down, I would simply gather more info when that error happens, either by changing its code in Firefly.Box.Data.Entity or with an error handler - I would gather the columns of the entity and compare their original values to their actual values to see which column has changed that have caused this exception - and continue from there

Noam Honig  

Founder & CEO

www.fireflymigration.com

--
You received this message because you are subscribed to the Google Groups "Migrated By Firefly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to migrated-by-fir...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/migrated-by-firefly/10bb892a-2d28-416b-bd76-657361f60cc1n%40googlegroups.com.

[Ludo Kosters]

Hi,

Something that comes to mind, do you perhaps have a local column in your task, something like below, which is added to the column collection of the task?

readonly BoolColumn V_SomeColumn = new BoolColumn();

And perhaps its value is set somewhere, for example in the OnEnterRow or OnLeaveRow?

I think that can trigger the SavingRow if V_SomeColumn does not have the property OnChangeMarkRowAsChanged set to false and you are updating its value without using SilentSet, even when the actual record is unaffected.

Hope this helps,

Ludo