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
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
There is a quirk in this mixin: if you upsert a model (i.e. you just know the id and properties, but you don't want to find it first) the createdAt-Timestamp is updated, too. This must not happen, of course.
I fear it's related to the lb-ds-juggler's implementation of default values.
Can you think of a solution besides querying for the model everytime?
See PR #10 for a breaking test. I'm not even sure if this can be fixed in the mixin. If not, it should at least be clearly stated in the readme.
The text was updated successfully, but these errors were encountered:
0ff
changed the title
createdAt will be updated on upsert (findOrCreate) callcreatedAt will be updated on upsert (updateOrCreate) call
Jun 5, 2015
There is a quirk in this mixin: if you upsert a model (i.e. you just know the id and properties, but you don't want to find it first) the createdAt-Timestamp is updated, too. This must not happen, of course.
I fear it's related to the lb-ds-juggler's implementation of default values.
Can you think of a solution besides querying for the model everytime?
See PR #10 for a breaking test. I'm not even sure if this can be fixed in the mixin. If not, it should at least be clearly stated in the readme.
The text was updated successfully, but these errors were encountered: