Editing the Database Initialization File or Unencrypted Database File
Some advanced users may decide to edit the database initialization file, for example to reorder the list of encrypted databases displaying in the Console window or to add a user-defined database for use in Console Mode. It is important to understand that changes to this file impact the database caching process used in Graphical Mode.
The following recommendations are also applicable if you edit an unencrypted database file, which includes user databases and free databases such as PURE5 or PG35.
Best Practice Recommendations
If you edit the database initialization file (tc.initd.tdb in Windows or initd.tdb in Mac and Linux), then:
- If a user database is added to the file, it is subject to the same caching as the encrypted databases. This means that further changes (to the user database) are not detected when you are working with databases in the System Definer in Graphical Mode.
If you have a user database, which is subject to regular updates, then:
- If you make changes to a user database, you then need to clear the cache.
- It is recommended that you create a separate directory to store unencrypted database files.
If you edit an unencrypted database file included with the installation (such as the PURE5 and PG35 files):
- Do not edit the file in the installation folder. Instead make a local copy and load it into the application as a user database.