-
Notifications
You must be signed in to change notification settings - Fork 617
Default values in entities are not used, potentially causes NullPointerExceptions #2565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type: bug
A general bug
Comments
I tend to agree this is a bug. |
I tend to agree with you and Michael. 🙂 |
meistermeier
added a commit
that referenced
this issue
Jul 13, 2022
meistermeier
added a commit
that referenced
this issue
Jul 13, 2022
Allows to use default values in the entity classes. Closes #2565
Thanks for reporting this. This was something I had not realised before. |
meistermeier
added a commit
that referenced
this issue
Jul 14, 2022
Allows to use default values in the entity classes. Closes #2565
meistermeier
added a commit
that referenced
this issue
Jul 14, 2022
Allows to use default values in the entity classes. Closes #2565
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SDN does not respect default values set in entities. This differs from OGM's behavior.
For example, say you have an entity like this
And you create a new node without the
active
andage
propertiesWhen you query for the node,
active
will befalse
andage
will benull
As far as I know, this example has never worked correctly in SDN. Specifically I tried this with 6.3.1 and 6.2.0 and saw the same behavior.
However, this differs from OGM, which uses the default values set in an entity. The tests in this project would pass if run using OGM.
This seems similar to #2348
The text was updated successfully, but these errors were encountered: