Hey there,

To start, it would be great if you could provide some specific details.

The issue with SQLite, unlike MySQL, is that all foreign key constraints must be added to the tables at their creation time. In contrast, MySQL allows these constraints to be added after the tables have been created, so the order in which tables are created does matter.

Currently, the tables are just queried using the following MySQL query:

SELECT TABLE_NAME
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = SCHEMA()

and looped through. While the tables are created, SQLite foreign key checks are disabled

Calculating a vector that would support arbitrary foreign key constraint creation would be quite complex, and I haven’t even attempted it.

TL;DR: SQLite doesn’t support ALTER TABLE … ADD CONSTRAINT … FOREIGN KEY

Thanks so much for taking the time to explain the origins of this problem. I didn't realize that SQLite3 doesn't have that capability at the moment. I have been using SQLPro for SQLite on a Mac and the app allows for the creation of foreign keys after the fact, likely doing all the work behind the scenes to create a new table with foreign key constraints and then copying all the data over before dropping the original table. Learning something new every day ...

@langrock, would you be kind enough to check out PR #98? It includes table creation order computation with foreign key constraints. Could you please test if it works with your problematic database?