updateOrInsert 是Laravel 中通過單個(gè)數(shù)據(jù)庫查詢實(shí)現(xiàn)“存在則更新，否則插入”的高效方法，1. 它不觸發(fā)模型事件、不自動(dòng)處理時(shí)間戳、不返回模型實(shí)例；2. 需手動(dòng)指定created_at 和updated_at；3. 適用於無需模型邏輯的高性能場(chǎng)景，如API 同步或設(shè)置更新；4. 只能用於查詢構(gòu)造器，返回布爾值表示操作是否成功。

The updateOrInsert method in Laravel is a handy way to either update a record if it exists, or insert a new one if it doesn't — without triggering model events like created or updated . It's efficient because it uses a single database query and doesn't load the model into memory.

Here's how to use updateOrInsert properly:

? When to Use updateOrInsert

Use updateOrInsert when you want to:

• Avoid extra queries (like checking existence first)
• Skip model events and observers
• Perform simple upsert-like logic directly at the query builder level

?? Basic Syntax

 DB::table('users')->updateOrInsert(
    ['email' => 'john@example.com'], // Conditions to find the record
    ['name' => 'John Doe', 'age' => 30] // Data to update or insert
);

How it works:

• If a row exists with email = 'john@example.com' , it will be updated with the second array.
• If no matching row is found , a new row is inserted with both the condition fields and the update fields.

So the resulting insert would be:

 INSERT INTO users (email, name, age) VALUES ('john@example.com', 'John Doe', 30);

? Real-World Example

Say you're syncing user preferences from an external service:

 DB::table('user_preferences')->updateOrInsert(
    [
        'user_id' => 123,
        'setting_key' => 'theme',
    ],
    [
        'setting_value' => 'dark',
        'updated_at' => now(),
        // 'created_at' won't be auto-set — you must handle it manually
    ]
);

?? Note: Unlike Eloquent models, updateOrInsert won't automatically set created_at or updated_at . You need to include them explicitly.

So better to do:

 $timestamps = ['created_at' => now(), 'updated_at' => now()];

DB::table('user_preferences')->updateOrInsert(
    ['user_id' => 123, 'setting_key' => 'theme'],
    ['setting_value' => 'dark', 'updated_at' => now()] $timestamps
);

? updateOrInsert vs firstOrCreate / updateOrCreate

? Use updateOrInsert for performance and simple queries .
? Use updateOrCreate when you need model events , accessors, mutators, or relationships.

? Key Points to Remember

• Works only on the Query Builder ( DB::table() or Model::query() )
• Returns a boolean : true on success, false on failure
• Does not fire Eloquent events
• Doesn't auto-fill created_at or updated_at
• Uses raw SQL under the hood — great for bulk or background jobs

? Pro Tip: Use with Models (but carefully)

You can call it on a model's query builder:

 User::query()->updateOrInsert(
    ['email' => 'sarah@example.com'],
    ['name' => 'Sarah', 'updated_at' => now()]
);

Still — no events, no model booting, no casts, etc.

So, updateOrInsert is fast and lightweight, perfect for stateless operations like API syncs, counters, or preference updates.

Basically: "Find by these fields, update with these values — or insert all together if not found." And that's it.

以上是如何在Laravel中使用UpdateOrinsert？的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！