Some further ideas
As a normal rule, if the database can do it for you, let the database do it for you. Databases know find out how to deal with knowledge about 453.7 occasions higher than you do. Don’t attempt to do their job.
In the event you ever really feel like including fields ending in 1, 2, 3, and so on., don’t. Learn up on normalization.
Use the right knowledge sort for a column. Don’t use a quantity for a boolean or a string for a date.
Strongly take into account including CreatedAt and UpdatedAt timestamp fields to each desk. You’ll be shocked at how typically you find yourself being glad that you simply did. Automate these timestamps with triggers, and they’ll grow to be helpful and painless.
Parameterized saved procedures are your mates. Use them as a lot as you possibly can.
Your question analyzer is an order of magnitude higher at deciding what’s the easiest way to question knowledge than you’re.
Watch out for booleans. Null turns booleans into quantum states—neither true nor false till somebody runs a question. Don’t use a boolean until precisely what null means in that context.
Don’t rely on string values to outline state. Use an enumerated worth as an alternative, guaranteeing that the information isn’t improper. Don’t let standing="bananna" trigger an error as a result of somebody fat-fingered a area.
I’ve left you with quite a lot of dos and don’ts right here. Once more, crucial takeaway is to choose a algorithm and implement them ruthlessly. Try this at the moment, and also you’ll save your self many complications down the street. Future you’ll thanks, imagine me.
