#eloquent — Public Fediverse posts

🗂️ Use #GoogleSheets as a #Laravel database! laravel-google-sheets-database-driver maps spreadsheet = DB, tab = table, row 1 = columns. Full #Eloquent & Query Builder support. #PHP #opensource
https://github.com/AmazingBV/laravel-google-sheets-database-driver

🗂️ Use #GoogleSheets as a #Laravel database! laravel-google-sheets-database-driver maps spreadsheet = DB, tab = table, row 1 = columns. Full #Eloquent & Query Builder support. #PHP #opensource
https://github.com/AmazingBV/laravel-google-sheets-database-driver

🗂️ Use #GoogleSheets as a #Laravel database! laravel-google-sheets-database-driver maps spreadsheet = DB, tab = table, row 1 = columns. Full #Eloquent & Query Builder support. #PHP #opensource
https://github.com/AmazingBV/laravel-google-sheets-database-driver

🗂️ Use #GoogleSheets as a #Laravel database! laravel-google-sheets-database-driver maps spreadsheet = DB, tab = table, row 1 = columns. Full #Eloquent & Query Builder support. #PHP #opensource
https://github.com/AmazingBV/laravel-google-sheets-database-driver

🗂️ Use #GoogleSheets as a #Laravel database! laravel-google-sheets-database-driver maps spreadsheet = DB, tab = table, row 1 = columns. Full #Eloquent & Query Builder support. #PHP #opensource
https://github.com/AmazingBV/laravel-google-sheets-database-driver

Album Review: Eloquent – “Sound Theatre”

In May 2026, synthpop duo Eloquent released the album, Sound Theatre.

http://aeschtunes.com/2026/05/21/album-review-eloquent-sound-theatre/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

Album Review: Eloquent – “Sound Theatre”

In May 2026, synthpop duo Eloquent released the album, Sound Theatre.

http://aeschtunes.com/2026/05/21/album-review-eloquent-sound-theatre/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

Album Review: Eloquent – “Sound Theatre”

In May 2026, synthpop duo Eloquent released the album, Sound Theatre.

http://aeschtunes.com/2026/05/21/album-review-eloquent-sound-theatre/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

55 Times in a 3 hour span is excessive even for a demented pyscho. In moments of anger or frustration i might do 5 posts in a day .

5150 in shells might be a good thing .

( The person must be deemed a danger to self (DTS), danger to others (DTO), or gravely disabled.) Fits?

#trump #cognitive #obama #nobelpeaceprize #eloquent #narcicissm
#mentalHealthMatters

55 Times in a 3 hour span is excessive even for a demented pyscho. In moments of anger or frustration i might do 5 posts in a day .

5150 in shells might be a good thing .

( The person must be deemed a danger to self (DTS), danger to others (DTO), or gravely disabled.) Fits?

#trump #cognitive #obama #nobelpeaceprize #eloquent #narcicissm
#mentalHealthMatters

55 Times in a 3 hour span is excessive even for a demented pyscho. In moments of anger or frustration i might do 5 posts in a day .

5150 in shells might be a good thing .

( The person must be deemed a danger to self (DTS), danger to others (DTO), or gravely disabled.) Fits?

#trump #cognitive #obama #nobelpeaceprize #eloquent #narcicissm
#mentalHealthMatters

55 Times in a 3 hour span is excessive even for a demented pyscho. In moments of anger or frustration i might do 5 posts in a day .

5150 in shells might be a good thing .

( The person must be deemed a danger to self (DTS), danger to others (DTO), or gravely disabled.) Fits?

#trump #cognitive #obama #nobelpeaceprize #eloquent #narcicissm
#mentalHealthMatters

Google sort une application de dictée par IA gratuite, et elle fonctionne sans internet, sauf que...
https://mac4ever.com/195546
#Mac4Ever #eloquent #Google

Google sort une application de dictée par IA gratuite, et elle fonctionne sans internet, sauf que...
https://mac4ever.com/195546
#Mac4Ever #eloquent #Google

Google sort une application de dictée par IA gratuite, et elle fonctionne sans internet, sauf que...
https://mac4ever.com/195546
#Mac4Ever #eloquent #Google

Song Review: Eloquent – “Checkered Past”

In April 2026, synthpop duo Eloquent released “Checkered Past,” the lead-off single from their album, Sound Theatre.

http://aeschtunes.com/2026/04/07/song-review-eloquent-checkered-past/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

Song Review: Eloquent – “Checkered Past”

In April 2026, synthpop duo Eloquent released “Checkered Past,” the lead-off single from their album, Sound Theatre.

http://aeschtunes.com/2026/04/07/song-review-eloquent-checkered-past/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

Song Review: Eloquent – “Checkered Past”

In April 2026, synthpop duo Eloquent released “Checkered Past,” the lead-off single from their album, Sound Theatre.

http://aeschtunes.com/2026/04/07/song-review-eloquent-checkered-past/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

Song Review: Eloquent – “Checkered Past”

In April 2026, synthpop duo Eloquent released “Checkered Past,” the lead-off single from their album, Sound Theatre.

http://aeschtunes.com/2026/04/07/song-review-eloquent-checkered-past/

#Music, #MusicReview, #Eloquent, #2020s, #2020sMusic, #Synthpop, #ElectronicMusic, #AeschTunes

#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

#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

#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

#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

#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

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 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

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

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

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

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

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

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

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

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

#Eloquent #Uncommon #Brilliance 6LeafLife #AllTheRage #AgainstTheMachine. Use it reflexively directly or indirectly. #Parabol vs parabola. Stay in side.

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

While there are many tutorials like https://dudi.dev/optimize-laravel-database-queries/ to create better queries to read data in Laravel, there are only very few to optimize writes.

Probably most underrated feature is "isDirty()" to save data only if it got changed, e.g.

// Retrieve a user from the database
$user = User::find(1);

// Change the name attribute
$user->name = 'Some Name';

// Save only if there are changes
if ($user->isDirty()) {
$user->save();
}

#laravel #eloquent

While there are many tutorials like https://dudi.dev/optimize-laravel-database-queries/ to create better queries to read data in Laravel, there are only very few to optimize writes.

Probably most underrated feature is "isDirty()" to save data only if it got changed, e.g.

// Retrieve a user from the database
$user = User::find(1);

// Change the name attribute
$user->name = 'Some Name';

// Save only if there are changes
if ($user->isDirty()) {
$user->save();
}

#laravel #eloquent

While there are many tutorials like https://dudi.dev/optimize-laravel-database-queries/ to create better queries to read data in Laravel, there are only very few to optimize writes.

Probably most underrated feature is "isDirty()" to save data only if it got changed, e.g.

// Retrieve a user from the database
$user = User::find(1);

// Change the name attribute
$user->name = 'Some Name';

// Save only if there are changes
if ($user->isDirty()) {
$user->save();
}

#laravel #eloquent

While there are many tutorials like https://dudi.dev/optimize-laravel-database-queries/ to create better queries to read data in Laravel, there are only very few to optimize writes.

Probably most underrated feature is "isDirty()" to save data only if it got changed, e.g.

// Retrieve a user from the database
$user = User::find(1);

// Change the name attribute
$user->name = 'Some Name';

// Save only if there are changes
if ($user->isDirty()) {
$user->save();
}

#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

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

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

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

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

Turned a weekend hack into a 1000× speedup: importing Firefox’s places.sqlite went from 4h ➝ 10s. 300k+ rows, clean architecture, future-ready stats. Full story here: https://reifschneider.digital/blog/taming-sqlite

#databases #performance #firefox #eloquent #mariadb #charm

Christine Jorgensen was so eloquent.

https://www.youtube.com/watch?v=fyh8BxPxtnw

#sofiaflorina #ソフィアフロリナ #transgender #transgenders #transwoman #transwomen #christinejorgensen #interview #interviews #lgbt #lgbtq #lgbtqia #lgbti #eloquent #queer

Christine Jorgensen was so eloquent.

https://www.youtube.com/watch?v=fyh8BxPxtnw

#sofiaflorina #ソフィアフロリナ #transgender #transgenders #transwoman #transwomen #christinejorgensen #interview #interviews #lgbt #lgbtq #lgbtqia #lgbti #eloquent #queer