Logical reorganization of the database occurs during a debug session that refers to a model that does not match the schema of the physical database.
During logical reorganization:
Database-only members are ignored during the debug session.
Model-only members are accessible during the debug session, but they are not read from or saved to the database.
Array members that do not match are accessible during the debug session, but they are not read from or saved to the database. They are only session-persistent and are created with a default value, corresponding to their Initial Value property.
Non-primitive members (that is, composite members that are stored as a single column in the database) that do not match are not read from or saved to the database. They are only session-persistent and are created with a default value, corresponding to their Initial Value property.
Members with a primitive property that does not match the database are accessible during the debug session, but they are not read from or saved to the database. They are only session-persistent and are created with a default value, corresponding to their Initial Value property.
Members with a length property and/or decimals property that do not match the database are accessible during the debug session, and are read from and written to the database, but they are truncated to shorter of the model-defined and database schema-defined lengths and/or decimals.
If the model-defined length is shorter than the database schema-defined length or decimals, the value written to the database is padded with spaces or zeros, as appropriate.