-
Notifications
You must be signed in to change notification settings - Fork 98
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
NPE with @Table(includeNullColumns=true and fieldsFormatSetAnnotation) #315
Comments
thanks for reporting! |
Issue is fixed by d2fe787 |
Thanks very much! I've tried my test once more. The test itself seems to run smoothly now, but it seems that there is still a similar issue during the report creation:
Best regards, |
Ok, I will create a more complete test case. |
I could not reproduce the issue. Could you provide a minimal example that causes the problem? |
Sure, I hope I can do this tomorrow morning. |
I think it might depend on your formatter implementation. The problem might be that your formatter implementation returns null where it should not. This, however, is also not documented in the API. |
Oh, this indeed could be the case - let me should doublecheck this. |
Very good catch, this indeed is the case, I'm returning null instead of blank in one used formatter. Changing this solves the issue. Maybe the exception thrown there could be improved to give a hint in the right direction? |
Yes, definitely. And the documentation should be more clear about this. |
Using @table with includeNullColumns = true and a fieldsFormatSetAnnotation results in a NPE when a column value really has null values:
using includeNullColumns=false not using fieldsFormatSetAnnotation solves this issue.
Best regards,
Niko
UPDATE: it seems that includeNullColumns not always solved the issue. Using a @NamedFormat on a
update: it seems that includeNullColumns not always solved the issue. Using a @NamedFormat on anull value (even when null is covered in the formatter implementation) still triggers the NPE.
The text was updated successfully, but these errors were encountered: