Change Tables in Studio (Magic xpa 3.x)
This property determines whether a Magic xpa project in Development mode can alter the table structure of an underlying database table.
If Change Tables in Studio is checked, then when you make some change to the table definition in the Data repository, Magic xpa will automatically take care of converting the actual table. Magic xpa will convert the actual data (if any exists) and also the definition of the table within the DBMS.
The default for this property depends on the type of database selected in the Default Database property of the Environment dialog box. If the Default Database is an SQL-type database, then the default for the Change Tables in Studio property will be a ‘not selected’ check box. If the Default Database is an ISAM-type database, then the default for the Change Tables in Studio property will be ‘selected’.
The default may be set to a ‘selected’ check box when building the table structure, before data is entered, and before the project goes into production.
During development, It is recommended to have this check box selected. Magic xpa will then ensure that its definition and the physical table structure are the same.
This property is not supported when modifying the structure of the following databases:
-
Memory tables – The table will be deleted and created in the new structure.
-
Local tables – The tables will remain in the original format. The data will be converted on the first access to the server.
-
GigaSpaces tables – When using an embedded space, the space will be restarted. When using a non-embedded space, you need to restart the space in order to apply the structure changes.
How Do I Account for Incompatibilities in Table Structure Between Magic xpa and the Database?
