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

Repeating schema auto-creation after failed commit causes NPE #54

Closed
tzaeschke opened this Issue Jan 30, 2015 · 1 comment

Comments

Projects
None yet
1 participant
@tzaeschke
Copy link
Owner

tzaeschke commented Jan 30, 2015

See Test_038_SchemaAutoCreate.testSchemaAutoCreationBug_Issue_54().
If an auto-created schema cannot be commited because of a commit() failure (for example unique index clash) then a second attempt at auto-creating the schema causes an NPE during the next commit while serializing the instance that causes the auto-creation.

The reasons is that a call to refreshSchema() during the first failed commit does not properly refresh the schema. It fails to re-associate fields from super-classes and does not refresh the associated Java-Fields.

tzaeschke added a commit that referenced this issue Jan 30, 2015

@tzaeschke tzaeschke added the bug label Jan 30, 2015

tzaeschke added a commit that referenced this issue Dec 18, 2018

@tzaeschke tzaeschke added this to the 0.5.2 milestone Dec 18, 2018

@tzaeschke

This comment has been minimized.

Copy link
Owner

tzaeschke commented Dec 18, 2018

Fixed for 0.5.2

@tzaeschke tzaeschke closed this Dec 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment