Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I used ImprovedNamingStrategy in hibernate, to mapping Java field name to MySQL column name.
ex) birthDate field -> birth_date column, AccountRole class -> account_role table
I’m doing test migrating hibernate code to eclipselink code.
What is the equivalent in EclipseLink to hibernamte’s ImprovedNamingStrategy ?
I don’t think there is an equivalent.
Where are you using this? For auto-mapping? You could use a JPA tool (such as Eclipse Dali) that will generate the JPA orm.xml or annotations from an object model, they may give more control over how the data model is generated.
In general using JPA but not the standard naming default will not be portable. If you want a mapping to use something different than the default, you should use the @Column annotation or xml.