[EMAIL PROTECTED] wrote:
Third issue is the collation. MySQL exports 'collate latin1_german1_ci'
what SQLite tries to handle but cannot since it only supports BINARY,
REVERSE and NOCASE collation.
You can create the latin1_german1_ci collation using the
sqlite3_create_collation() API.
I have 4 tables with exactly the same design.
I then tried to create the second table and got an error with the CREATE
INDEX statements since an index with the same name already existed.
SQLite3 seemingly stores indexes (their metadata) on a per DB basis and
not on a per table basis as MySQL does.
Correct. You cannot have two or more indices with the same
name. If you did have more than one index with the same name,
SQLite would have no way of knowing which index you meant when
you say things like "DROP INDEX xyz".
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
