#DelegatedTypes in #Laravel — Smarter Alternative to STI #PHP #Eloquent #opensource #webdev

🏗️ Model class hierarchies via polymorphic relationships & delegation — composition over inheritance, done right

🧵👇

🔄 Each subtype keeps its own table while sharing a common root Entry model — no more nullable column bloat like with STI
🎯 Comments, likes & reactions attach to the Entry — one route, one controller, no endpoint explosion

EagerLoadingでLaravelのN+1問題を解決するテクニック
https://qiita.com/Fukuda_Genee/items/6ff6bf3c378779dd217f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #PHP #Laravel #初心者向け #ORM #Eloquent

Eloquent relationships — let AI get them right every time. 🧠

Describe your data structure in plain English:
"User has many Posts. Post belongs to User and has many Comments. Comment belongs to Post and User."

LaraCopilot generates:
→ All three models with correct method types
→ All foreign keys in migrations
→ Eager loading in controllers

Describe it. Get it right. First time.

#Laravel #Eloquent #PHP

Eloquent Guard: как ловить N+1 и медленные запросы в Laravel, не зарываясь в vendor

Проблема N+1 стара как мир. Инструментов много: Debugbar хорош локально, Telescope тяжеловат для продакшена. Мне хотелось решения, которое будет «стучать» в Slack или Telegram именно тогда, когда проблема случилась на проде, и при этом сразу показывать пальцем на виновную строку кода.

https://habr.com/ru/articles/1010822/

#laravel #eloquent #php #sql #mysql #postgresql #database_optimization #database_performance #database_monitoring

Обновлена статья о коллекциях Laravel:

Узнайте, как использовать Коллекции Laravel для фильтрации, преобразования и оптимизации работы с данными. От основ (filter, map) до продвинутых техник: ленивые коллекции, макросы и операции сведения.

https://www.dev-notes.ru/articles/laravel/collections/

#Laravel #Collection #Eloquent #PHP

Uff, I've been bit by a quirky Eloquent issue. The worse part is that I know why it happens but I don't know how to "fix it" (I've found a workaround, but Id like to prevent it from happening in the future, ideally with a patch upstream).

It involves relationships, macros for the Builder and eloquent silently overriding an `id` column because the results from the SQL query contain 2 different `id` columns (because of a join).

I'll try to create a sample project with minimum code to reproduce and see if I can manage a fix.

#Laravel #Eloquent

Doctor reveals the 1-minute daily hack that can radically improve public speaking skills

https://fed.brid.gy/r/https://www.upworthy.com/how-to-get-better-at-public-speaking

A great option to optimize database writes in Laravel is using bulk operations.
E.g. "upsert()" can insert/update multiple rows with _one_ query using "on duplicate" logic:

User::upsert(values: [
['email' => 'foo@domain', 'name' => 'Foo'],
['email' => 'bar@domain', 'name' => 'Bar'],
], uniqueBy: ['email'], update: ['name']);

becomes:

INSERT INTO users (email, name),
VALUES
('foo@example', 'Foo'),
('bar@example', 'Bar')
ON DUPLICATE KEY UPDATE name = values(name);

#laravel #eloquent

When adding the type for the Query Builder that's passed as an argument to an Eloquent's scope, do you use `Illuminate\Database\Eloquent\Builder` or `Illuminate\Contracts\Database\Eloquent\Builder`.

I just realized they were being used interchangeably on a project I've been working on.

My initial thought would be to use always the contract (the interface is implemented by `Eloquent\Builder` and by `Eloquent/Relations/Relation`), but looking at the docs, the official stance is to import the Builder object 🤔

https://laravel.com/docs/12.x/eloquent#local-scopes

Any thoughts?

#Laravel #Eloquent #PHP