TurboDB Engine Documentation Upgrade to TurboDB Win32 v6 |
Previous Top Next |
When upgrading from TurboDB 5 to TurboDB 6 you must take care of the following issues:
Language Drivers
TurboDB 6 does not support language drivers anymore. Instead, tables and columns can have collations, which define the sorting of strings. When you want to upgrade a table to TurboDB 6 which uses a language driver, you must remove the language driver using TurboDB 5, upgrade the tables to level 6 using TurboDB 6 and assign the desired collations.
String Sorting and Comparison
Strings are now sorted and compared according to their collation. Since sorting and comparison were different in TurboDB 5, comparison of strings in older tables is now case insensitive. If that does not fit your requirements, assign another collation.
Important Hint
Please note, that TurboDB 6 cannot share TurboDB databases with TurboDB 5 at the same time. You will receive an error message saying the locking files are incompatible. If there is no TurboDB 5 application currently running, but there are still net/rnt/mov/rmv files around, the same error will shine up. Delete the files and everything will work as expected.
When upgrading from TurboDB 4 to TurboDB 5 some points have to be considered:
Important Hint
Please note, that TurboDB 5 cannot share TurboDB databases with TurboDB 4 at the same time. You will receive an error message "Error in log-in". If there is no TurboDB 4 application currently running, but there are still net/rnt/mov/rmv files around, the same error will shine up. Delete the files and everything will work as expected.
New Reserved Keywords
The following identifiers are new reserved keywords in TurboDB 5. If your database schema is using those words as table or column names, you must either enclose them in double quotes wherever they appear in SQL statements or use different names:
ACTION, ALL, ANY, CASCADE, CASE, CAST, DICTIONARY, ENCRYPTION, EXCEPT, EXISTS, FULLTEXTINDEX, INTERSECT, NO, SOME, TOP, UNION, WHEN
Use of Quotes
TurboDB 5 uses single-quotes to denote string literals exclusively. Double quotes were allowed in TurboDB 4 as well but must be changed when upgrading. Double quotes now exclusively denote identifiers and can be used to work with names that contain spaces or are identical to reserved keywords.
Encryption
TurboDB now supports additional methods for strong encryption. Due to this fact the syntax of the create table statement and the alter table statement has been modified.
Full-Text Indexes
Full-text indexes have been thoroughly re-designed to be faster and maintained. The old full-text indexes are still supported for the older table levels but if you want to upgrade your tables you have to re-write the full-text part of your SQL code.