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
This is more of a note as I'm unsure of the intended behaviour.
Currently when you've got a property with a default value under change tracking you'll get no entry in case you don't provide a value. In case you supply a value, you'll get an entry with the create modification.
So e.g. if there's something in that direction:
entitySomething {
key ID:UUID;
@changelogSomeFlag:Association to Flagdefault'X';
}
As far as I can see if you don't provide the value for SomeFlag you'll not get a create change entry.
The text was updated successfully, but these errors were encountered:
Hello @tsteckenborn
the differ, which catches changes works on Request/Service Entity level, while default values are implemented at the DB-driver level, so there is no straightforward way to identify it. From the perspective of the plugin, the SomeFlag property of the request is empty.
We would actually need to intercept the generated INSERT statement two levels deeper and compare it to the request, which wouldn't be feasible.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
This is more of a note as I'm unsure of the intended behaviour.
Currently when you've got a property with a default value under change tracking you'll get no entry in case you don't provide a value. In case you supply a value, you'll get an entry with the
create
modification.So e.g. if there's something in that direction:
As far as I can see if you don't provide the value for SomeFlag you'll not get a
create
change entry.The text was updated successfully, but these errors were encountered: