You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hoping it might be possible to revisit the changes in PR #34836. With those changes, Laravel now invokes the setKeysForSaveQuery() method every time an Eloquent model calls fresh() or refresh(). In my case, this broke a ton of code, since I'm currently overriding that method for my implementation of optimistic locking on certain records.
I can change my implementation of the locking logic easily enough, but before I do that, I wanted to just raise a flag, since this seems like an abuse of the setKeysForSaveQuery() method. Should Laravel really be calling that method outside of a save query? Calling it during fresh() or refresh() is unexpected based on the method's name.
Steps To Reproduce:
N/A
The text was updated successfully, but these errors were encountered:
@taylorotwell Thanks for the reply. That would be a lot clearer and semantically consistent, IMO. I can put together a pull request for that if you'd like.
Description:
I'm hoping it might be possible to revisit the changes in PR #34836. With those changes, Laravel now invokes the
setKeysForSaveQuery()
method every time an Eloquent model callsfresh()
orrefresh()
. In my case, this broke a ton of code, since I'm currently overriding that method for my implementation of optimistic locking on certain records.I can change my implementation of the locking logic easily enough, but before I do that, I wanted to just raise a flag, since this seems like an abuse of the
setKeysForSaveQuery()
method. Should Laravel really be calling that method outside of a save query? Calling it during fresh() or refresh() is unexpected based on the method's name.Steps To Reproduce:
N/A
The text was updated successfully, but these errors were encountered: