#Laravel Tip: Queries that need to examine string columns will always be slower than integer columns (even when indexed). Therefore, when storing data, consider whether you need to keep the string representation... 👇 example in link below

🔥 #Laravel Tip: Instructing the database to delete a huge number of records is likely to make it fall over (esp. when using cascade deletion). However, you can avoid this by staggering the process into batches and adding pauses to allow the database time to catch up.

🌶️ #Laravel Tip: Prefer Eloquent over Query Builder when performing updates, inserts, etc. When using Query Builder to update a record in DB, $fillable, $guarded, & the rest of Eloquent goodies are ignored. https://t.co/mi0YBvEP5z #Laravel #PHP #development

#Laravel tip 🔥 virtual generated column

#Laravel #Database Tip: On v9.18 you can get notified when the application spends too much time querying the database during a single request. Add `whenQueryingForLongerThan` closure in the boot method of `AppServiceProvider`. 🔗https://t.co/KqffBUc8Lx #Laravel #Database #PHP

🔥 #Laravel Tip: Here’s a simple, but important one… particularly if you’re new to the framework. Make sure that aggregations are done within the DB and not Laravel. Go even further with indexes and WHERE constraints:

👉 Get all the column names for a table in #laravel

#Laravel Tip💡 You can validate the uniqueness of a DB column for a particular user. Let's say, the posts table has slug and user_id, and slug must be unique per user_id. i.e. composite unique key of slug and user_id

⚡️ Database Tip Creating indexes is a handcraft learned from experience, multiple-column indexes is a lot more complicated. But it doesn't have to be complicated! Here are 3 simple rules for the column ordering of multiple column indexes, solving 80% of the perf problems.