Filament ignoring foreign key constraints
Pretty simple, i have a foreign key constraint on a table, but filament is able to delete records i'm not allowed to delete in the database? Is there some sort of option I need to enable?
CSorry, what do you mean
I don't think it's possible for filament to know what constraints you have in the database. You will have to either check manually or add some sort of validation.
filament is able to delete records i'm not allowed to delete
I don't think it's possible for filament to know what constraints you have in the database. You will have to either check manually or add some sort of validation.
DI mean..
Dsomehow filament disables the constraints?
Di was expecting a 500 error, but i was allowed to delete it
Dwhich is super weird imo
CIf you have a constraint in the database (I assume a foreign key or something similar), filament should not be able to remove it, unless they do some REALLY funky stuff behind the scenes - which I doubt.
Are you sure there's not something else going on?
Are you sure there's not something else going on?
CCan you give add some examples? Like the migration definition and the code that should fail?
Dcode is just a basic delete action on the store resource
Dand then i have these constraints:
Di would love to know why these don't work for filament
AShouldn’t you have ->constrained() on there too? Or use ->restrictOnDelete()
Solution
Di found out why it didn't work, i was using soft deletes 
