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
When using a virtual column that modifies a primary key, if the primary key is not supplied on an update, the pk is null and the virtual column will try to operate on that null value. The value should always have a value?
I think it makes sense that under the hood a new record is made and then updated with the existing record, however the null id is problematic since our virtual getter is trying to calculate a value on something that shouldn't be null... :(
The text was updated successfully, but these errors were encountered:
When using a virtual column that modifies a primary key, if the primary key is not supplied on an update, the pk is
null
and the virtual column will try to operate on that null value. The value should always have a value?Given a model like
then when the update is called on a record that exists already, the console.log of this will print something like:
I think it makes sense that under the hood a new record is made and then updated with the existing record, however the null id is problematic since our virtual getter is trying to calculate a value on something that shouldn't be null... :(
The text was updated successfully, but these errors were encountered: