Hi, I usually consider putting a ON DELETE CASCADE & ON UPDATE CASCADE on foreign keys to be a good practice. I'm happy to have the database-layer ensure referential integrity.
Reading some past discussions on this google group seems to confirm that. (I would be glad to understand if/how it can be nuanced though) While reading the Sequel docs, I realized that the `create_join_table` method does not include those cascading options on the foreign keys it creates though (nor an option to include them). Is there a reason why it is unnecessary or should not be done in this case? Or maybe it is a place where the Sequel API could be extended? Thanks, Michael -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/cac53140-1bac-40e6-95ec-2f381c20cfc0%40googlegroups.com.
