Hi, I'm just trying to port some MySQL-4.1.5-gamma DB to SQLite3. I exported the MySQL-DB-Metadata using PHPMyAdmin and SQLite did not accept it for several reasons. One reason is MyAdmin exports colum-names in "strange" quotes. There's IMHO no urgent need for SQLite to process these. Next issue is, SQLite3 does, according to it's documentation, not handle the KEY keyword in CREATE TABLE statements. I took these out of the CREATE TABLE statement and changed them to single CREATE INDEX statements. 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. I thought the original collate statement is simply stored in the sqlite_master-table for that column, but I get an error and have to take it out of the MySQL-generated SQL-statement too. 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.
Just to mention...Comments? Best, Bernhard
