We're using JPA and will be happy to set the relevant fields as @Enumerated(EnumType.STRING). It's my understanding that in that case, Hibernate will (now) just try to push the value's name into SQL as a string and read it out of the ResultSet as a string, so that PGobject's transparent translation should accommodate the whole affair. Is this the hoped-for behavior?
I'll be happy to give a new version a try. We're using Maven and are currently on 3.6.10; what do we need to be aware of if we're upgrading all the way to a 4.1?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
We're using JPA and will be happy to set the relevant fields as @Enumerated(EnumType.STRING). It's my understanding that in that case, Hibernate will (now) just try to push the value's name into SQL as a string and read it out of the ResultSet as a string, so that PGobject's transparent translation should accommodate the whole affair. Is this the hoped-for behavior?
I'll be happy to give a new version a try. We're using Maven and are currently on 3.6.10; what do we need to be aware of if we're upgrading all the way to a 4.1?