Follow-up. All went well for the Hibernate reverse engineering using “native” when I was mapping to MySQL, but when I actually got around to attempting the same thing in Oracle, I got an exception stating that it couldn’t retrieve the next number for auto-increment. For Oracle, I switched to “increment” and all worked well. As I have to move forward with the project, I’ll accept it for now with the hope that I can try to figure out why at some point.
Here’s a tip for anyone reading this and using Hibernate and mapping the elements of an XSD (schema) file to a database. If you have the luxury, try to match the element names of the XSD/XML to exactly the same column name in the database. Of course, this is not always possible. I’m developing a horse race handicapping program from scratch and it’s gone fast because of this mapping technique. At work, both the database schema and the XSD schema originated with other companies and were forced on us. The matches are vague at best and non-existent at worst. It’s been like trudging through a swamp with the latter.