@MrPunyapal One way around that is to use computed columns. That way you can index that column and get away with filtering on the year alone. Like always it depends on the need.
@patilvishi Select your gift from the basket.
From the basket select your gift.
I think the ”natural” flow is how you structure a sentence in you native language.
For example in german the verb is the last word in the sentence.
Your gift from the basket select.
@Akintola_steve It depends, but I think of ORMs as a way to make the code more readable, and complex queries makes a mess regardless if you use ORM och plain SQL.
In such cases I use views, and then I can keep the ORM simple and readable, and tuck the SQL into a migration
@neerajjj6785 Json should almost never be used inside the database. The only reason I see valid for storing it there, is when you receive a big payload from an API and you process it with a schedule job, rather them at once.
@Umesh__digital If you have one key in your pocket, it's fast to get it, if you have 100 keys in your pocket, how long does take to get the correct key?