Type mapping of @ColumnResult is ignored
Instead of a "null", the mapped column.type() argument of @ColumnResult should be used.
My apologies I see is still open. My unfamiliarity with this bug system.
Gail Badner - you closed my issue (), is that because it is really the same as this one? You didn't give a reason for closing it. Also, this issue is also marked closed. Does this mean that it won't be fixed.
To add to my issue (even though you closed it), I did try today to type each of the columns in the mapping (e.g. type=) but it didn't help. I updated the stack overflow question I had made. The link is in HHH-9445.
If this is bug, will it be fixed or should I find another way to do what I need to do?
Closing resolved issued in preparation for releasing 4.3.6.
, I've merged the PR to fix the issue in 4.3.6. I've also merged the changes to master, but the (newly added) tests fail there as you kind of assumed. I've created to fix the issue on master and re-enable the tests which I disabled for the time being via @FailureExpectedWithNewMetamodel.
, please go ahead and merge the fix from your pull request.
Also, please try running the test in your pull request on master. If it works, then please commit it using this JIRA issue.
If it doesn't work, then please create a new JIRA for fix version 5.0.0, mark the test @FailureExpectedWithNewMetamodel, and commit the test using the new JIRA issue.
Please resolve this issue when you're done. I plan to release 4.3.6 Wednesday afternoon or evening (Pacific time), so please resolve before then.