Eloquent associate() fails: undefined method on Query\Builder
Call to undefined method Illuminate\Database\Query\Builder::associate()Short answer
associate() belongs to belongsTo relationships only. The error means you called it on the wrong kind of relation, or on the loaded model instead of the relationship method. Call it on the relationship with parentheses, on the model that holds the foreign key, then save that model.
Fix it fast
1Find out which cause you have
Open the relationship you call associate() on and look at its return: belongsTo, hasOne or hasMany.
grep -n -A3 "function account" app/Models/User.php2Match what you see, then jump to its fix
- 1
The relationship method returns hasMany() or hasOne(), and the model you hold is the parent.associate() is called on a hasOne, hasMany or other non-belongsTo relationFix - 2
The code reads $user->account->associate(...) without parentheses after account.associate() is called on the loaded property instead of the relationship methodFix
- 1
What does the error look like?
Call to undefined method Illuminate\Database\Query\Builder::associate()
Cause 1 of 2
associate() is called on a hasOne, hasMany or other non-belongsTo relation
1Check
The docs describe associate() under the belongsTo relationship: it sets the foreign key on the child model. A parent that owns the foreign key in another table has no such column to set.
grep -n "belongsTo\|hasMany\|hasOne" app/Models/*.php2Fix
Call associate() on the child (the model whose table holds the foreign key). From the parent side, add children with the relationship's save() or create() instead.
// child side: Comment belongsTo Post
$comment->post()->associate($post);
$comment->save();
// parent side: Post hasMany Comment
$post->comments()->save($comment);3Verify
The foreign key column now holds the parent's id.
SELECT id, post_id FROM comments ORDER BY id DESC LIMIT 1;Confirmed by laravel.com
Cause 2 of 2
associate() is called on the loaded property instead of the relationship method
1Check
$user->account returns the related model (or null), while $user->account() returns the relationship object. The docs call associate() on the second form.
grep -rn "->associate(" app/2Fix
Use the relationship method with parentheses and save the model afterwards. associate() only sets the foreign key in memory.
$account = Account::find(10);
$user->account()->associate($account);
$user->save();3Verify
Read the foreign key column in the database.
SELECT id, account_id FROM users WHERE id = 1;Confirmed by laravel.com
How do I stop it coming back?
- Declare relationship return types (BelongsTo, HasMany) so the editor flags a wrong method.
- Remember the direction: associate() on the child, save()/create() on the parent.
- Always call save() on the child after associate().
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Back end
Composer says the gd extension is missing on a Laravel project
composer install or composer update stops on a package that requires ext-gd
Composer refuses to install a package that requires ext-gd when the PHP binary running Composer has no GD extension.
4 causes, each with a fixBack end
composer require maatwebsite/excel fails to install
Composer says the package needs an older PHP than the one installed
Composer refuses maatwebsite/excel when the PHP version or a PHP extension does not match what the package and PhpSpreadsheet need.
3 causes, each with a fixBack end
composer install says the lock file is not compatible and asks for update
Your lock file does not contain a compatible set of packages. Please run composer update.
composer install checked the locked packages against this machine's PHP and extensions and found a conflict.
3 causes, each with a fixBack end
composer require laravel/horizon fails: ext-pcntl is missing
laravel/horizon v1.1.0 requires ext-pcntl * -> the requested PHP extension pcntl is missing from your system
Horizon needs the pcntl extension, and Composer refuses to install it where PHP lacks that extension.
3 causes, each with a fixBack end
composer require laravel/passport stops with 'requirements could not be resolved'
... but these were not loaded, likely because it conflicts with another require.
Composer found no Passport release that fits your project at once.
4 causes, each with a fixBack end
Composer says the root composer.json requires a PHP version your PHP does not satisfy
Your requirements could not be resolved to an installable set of packages.
Composer compares the php constraint in your composer.json, or in a package, with the PHP that runs Composer.
3 causes, each with a fix