Level 122
updateOrInsert is a QueryBuilder method ?
Jul 3, 2022
11
Level 2
updateOrCreate not touching timestamps?
Hello,
I have a question of my own. It seems that updateOrCreate doesn't touch created_at and updated_at when creating a new row. I'm very surprised, I don't recall such a behavior with Laravel.
Plus the documentation says:
The upsert method will automatically set the created_at and updated_at timestamps
This concerns the upsert method but how comes upsert and updateOrCreate have different behaviors?
My snippet:
Payment::updateOrInsert(
['charge_id' => $charge_id],
[
'user_id' => $user->id,
'price_id' => $price->id,
'status' => $status
]
);
Thanks
Level 2
@Snapey yes but as I was calling it from the ORM Payment::class model, I’d assume that I’d work fine
Level 122
@axeloz and if you use updateOrCreate ?
Level 102
@axeloz if a method does not exist in the eloquent builder for models, the call just gets forwarded to the regular query builder. This for instance what happens with toSql(). Regular insert would also work in eloquent, but would skip timestamps
Level 2
The upsert method doc is three lines below the updateOrCreate method in the ORM section of the doc. So you'd expect same behavior.
Level 2
@Sinnbeck yes but I suppose the method exists for ORM, this is in the documentation: https://laravel.com/docs/8.x/eloquent#upserts
Level 122
@axeloz but you are using updateOrInsert and then reading the docs for updateOrCreate
Level 102
@axeloz it uses updateOrCreate or upsert in those examples? You use updateOrInsert?
Level 122
upserts are something else (you are not using upsert)
Level 2
Level 102
Please or to participate in this conversation.