Repository navigation
Sync panics on sqlite named foreign key #3132
Description
Activity
I am finding usage very fragile.
The critical issue (mentioned above also) is panics from unexpected situations in sync code. Debug is a PITA.
When a table is altered via the RustRover built-in sql facility to match an alteration made in sea_orm I often get panics. Dropping the table and letting sync regenerate it works, but as the database evolves this wastes test data.
2.0.0-rc.41 (.42 is not usable for me, forget why)
If a foreign key has a name (not anonymous) sync panics, providing no context (e.g. which table, which key).
If I manually set a FK to have a name sync fails. Remove the name and it seems ok.
Default behaviour for FK generation in tools is to make a name. I think this is expected behaviour.