You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moved here from the (now private) original Sideboard issue tracker.
We currently have two tests for foreign key support where we make sure that deleting a row (especially over our CRUD API) cascades. This works on my machine but fails on some other machines, and some basic Googling shows that foreign key support is not always compiled into SQLite. Depending on your package your foreign key declarations in your CREATE TABLE statements may just be ignored in SQLite.
We should do two things:
confirm whether that's true before doing any work on this ticket, since I didn't spend enough time to be certain of what I was reading
detect whether SQLite has foreign key support compiled in, and only skip() if it isn't via the skipif decorator
The text was updated successfully, but these errors were encountered:
Moved here from the (now private) original Sideboard issue tracker.
We currently have two tests for foreign key support where we make sure that deleting a row (especially over our CRUD API) cascades. This works on my machine but fails on some other machines, and some basic Googling shows that foreign key support is not always compiled into SQLite. Depending on your package your foreign key declarations in your CREATE TABLE statements may just be ignored in SQLite.
We should do two things:
skipif
decoratorThe text was updated successfully, but these errors were encountered: