Hyperjaxb3 column naming override
GoogleCodeExporter opened this issue · 1 comments
GoogleCodeExporter commented
The specified column names in an XSD are not necessarily used in the generated
annotations. HJ3 seems to mangle the names in order to avoid conflicts with
reserved names for different DBMSs.
However, it is possible to override this behaviour using customisations.
Perhaps an idea for 2.0?
Original issue reported on code.google.com by freeke...@gmail.com on 3 Jul 2011 at 3:02
GoogleCodeExporter commented
Can you give more detail?
<orm:column name="CUSTOMER_ORDER__ID" nullable="true" />
etc works fine for me.
Thanks
Original comment by roger.parkinson35 on 22 Feb 2012 at 6:21