Laravel Truncate DB Table: 2 Ways to Avoid Errors 

Wouldn't the best solution be to set up on your game migration an onDelete effect ? Like cascade ? I'm making the assumption that truncate would work in that case though. Otherwise it feels like a hack because of the migration are not 'good enough'.

Brilliant... This information is going to come in handy.

You are the best ❤

Thanks!

good video! Random question...Do you have any recommendation of a Laravel book? Thank you Polivas!!

Hi Povilas, where is the best place to stay update with Laravel trick and update (ex. the last update in Laravel 11), where I can learn? Thanks

Hi Povilas. I have a project where I am making use of this feature (disabling and enabling FK checks) in the code. I still feel its not the best way or not safe. Once you disable the check, the entire DB is affected meaning the foreign key constraint can be violated somewhere in the database (since the checking is disabled). It would've been better if we could disable the check on specific table(s) and not at DB level. I haven't explored this yet but it would be nice to have this e.g. passing table(s) name as arguments

Could you also do the disable foreign key constraints and truncate with data still in the games table?

Is it really related to Laravel? I think it's a sql issue.

I use truncate always in testing.