Some extra ideas
As a common 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.
If you happen to ever really feel like including fields ending in 1, 2, 3, and many others., don’t. Learn up on normalization.
Use the proper knowledge sort for a column. Don’t use a quantity for a boolean or a string for a date.
Strongly contemplate 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’re going to change into helpful and painless.
Parameterized saved procedures are your pals. Use them as a lot as you may.
Your question analyzer is an order of magnitude higher at deciding what’s one of the best ways 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 you recognize precisely what null means in that context.
Don’t rely on string values to outline state. Use an enumerated worth as a substitute, guaranteeing that the info is rarely mistaken. Don’t let standing="bananna" trigger an error as a result of somebody fat-fingered a subject.
I’ve left you with plenty of dos and don’ts right here. Once more, an important takeaway is to select a algorithm and implement them ruthlessly. Try this right now, and also you’ll save your self many complications down the highway. Future you’ll thanks, imagine me.
