Linked Records with Cascade

It updates existing reference fields in plugin.rb so each link has an explicit on_delete rule. The template covers cascade for owned children, restrict for required children, and nullify for optional links. It also adds a user-facing note on the parent show page so delete behavior is visible before action.

Use cascade when the child record only makes sense as part of the parent, such as tasks under a project or line items under an invoice. Use restrict when deleting the parent would leave invalid or broken child records. Use nullify when the relationship is optional and the child can continue without the parent link.

No. It is an edit-mode template that changes existing reference field declarations and adds a delete-behavior message on the parent detail screen. It is meant for apps that already have linked records in place and need safer deletion rules.

A builder or admin who understands the record model and can tell which relationships are owned, required, or optional. It is especially useful when a plugin already has several reference fields and you want to avoid accidental orphaned data or unsafe deletes. If the data model is unclear, review the relationships before applying the change.

The most common mistake is marking a relationship as cascade when the child should be preserved, or restrict when users expect cleanup to happen automatically. Another pitfall is leaving the default nullify behavior on a required link, which can create orphaned records. The template is designed to force each reference field to be reviewed one by one.

Manual delete handling usually depends on someone remembering the right steps every time, which is easy to miss in spreadsheet-era workflows. This template puts the rule in the field definition itself, so the app enforces the same behavior consistently. That reduces orphaned records, broken links, and support issues after deletions.

Yes. The template is meant to be adjusted to your specific record relationships, not applied blindly. You can keep optional links as nullify, switch owned children to cascade, and use restrict where deletion should be blocked until dependent records are handled.

Yes. The prompt explicitly updates the reference field declarations in plugin.rb and adds a delete explanation on the parent show page. It also asks for small, targeted edits only, which makes it easier to fit into an existing plugin without rewriting unrelated files.

Review every reference field and confirm the intended lifecycle of the child record. Test deletes on a copy of the app with real-looking sample data so you can see whether cascade, restrict, or nullify behaves as expected. Also verify that the parent show page message matches the actual rule users will experience.