/
Migrating grids from the old gd.table property to the new gd.tablename property

Migrating grids from the old gd.table property to the new gd.tablename property

Introduction

To circumvent the issue where a tablename exceeds the oracle limitation of 30 characters for tablenames, we had to introduce a new property
gd.tablename.

This property will direct the plugin to create tables with following tablename structure

gd.tablename = familylist create table familiylist_c12345 ( ...)

This is much shorter than the previous <basename>_customfield_<customfieldid>_<contextid>
Grid configurations which are still using the old gd.table property will still work, but a warning will be added
indicating that the gd.table property is deprecated and should be replaced.

Migration procedure

The migration procedure is straightforward 

  1. remove the property gd.table from the configuration

  2. alter the tablename in the database

  3. add/replace the property gd.tablename to the configuration
     

We decided not to automate this migration as other applications might use this table

 

Example

For instance if the configuration was

... gd.table=xtable ...

This created the table xtable_customfield_12345_54321

You will have to modify the tablename equally into xtable_c54321 (dropping the customfield_12345_).  This can be done using a DDL query such as

alter table xtable_customfield_12345_54321 rename to externaltable_c54321

(all depends on the underlying database server) 

 

Change the configuration to

... gd.tablename=xtable ...