Jump to content

Recommended Posts

I told you once, I've been writing database apps using web technology for about 25 years.
About 20 years ago I gave up on identifying foreign keys in the database because apps kept crashing on me.

You suggested that I try it again.

Well, the app I'm working on is probably about 50K lines & 80 tables.
To do that would be some work BUT - my app allows users to create tables and dependent (slave) tables for them.
There could be up to 20 user defined tables. Coding for orphans and missing IDs was becoming a problem.
Because of your suggestion, the thought immediately occurred to me - hey, use foreign keys & cascades.

So, I did the work (and it wasn't that bad). Now my whole database uses foreign keys and SET NULL or CASCADE as needed.
I scrapped a BUNCH of code that handled orphans & missing IDs.
The app is working great.

Thanks so much for pushing that issue.

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.