Property in the work object is not getting saved to the database
An exposed property is not getting saved to the database column, although it is properly being saved to the BLOB.
Steps to Reproduce
- Define a property XY in child class P-c and expose the property in class P's table. Observe that proper column population is occurring.
- Determine that other subclasses of P need access to the property, for example P-c2, so define the property in parent class P but accidentally give it the wrong case, for example Xy. Observe that populating of the property in the table is no longer occurring.
- Attempt to remedy the situation by withdrawing property Xy in parent class P and defining correct case property XY. Observe that column population is still not occurring.
Withdrawing the wrong case property was insufficient.
Deleting the property from the database allowed the exposed column to be populated properly. In the example described above, deleting property Xy from the database resolved the issue.