When I use "MIGRATE DATABASE FROM ... WITH DATA" to migrate an dbisam 3 database, the full text index from a dbisam table is converted. But the index is case sensitive after the migration. How can I specify in the migration process to make the text index case insensitive? It seems all the full text index in dbisam 3 is case insensitive. Thanks, Paul

Paul,

<< When I use "MIGRATE DATABASE FROM ... WITH DATA" to migrate an dbisam 3
database, the full text index from a dbisam table is converted. But the
index is case sensitive after the migration. How can I specify in the
migration process to make the text index case insensitive? It seems all the
full text index in dbisam 3 is case insensitive. >>

This is a bug - the text index creation in the migration code is using the
collation/locale from the table being migrated, but isn't setting the CI
(case-insensitive) flag for the collation.

A fix will be in the next build, which will probably be next week.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim, My annual support plan has expired. In order to get this bug fix release, do I have to buy the annual support plan again? Thanks, Paul

Paul,

<< Tim, My annual support plan has expired. In order to get this bug fix
release, do I have to buy the annual support plan again? Thanks, Paul >>

Only if 2.05 was not released when you last purchased a support plan.  If
2.05 is available on your downloads, then no, you won't have to purchase a
new support plan.  Although, it's always nice if you do.

--
Tim Young
Elevate Software
www.elevatesoft.com