max wrote:
alpha 1 does not have that feature.
its on the roadmap for alpha 3.
May i ask what your usecase/reason is for reverse engineer parts of the schema ?
is it because it takes too long (some dbs has horrible jdbc metadata impl) ?
or just that you dont want to regenerate "on top" of existing code ?
(that can be managed by using meta tags in the generated hbm.xml ...which we need to add to the rev.eng.)
Hello Max,
Thank you for the response. Please let us know when we could expect Alpha 3.
We are using an Oracle 9.1.2 database with about 225 tables. Some of these tables (approx 10) are from older software packages and do not have primary keys. The tool is failing on those tables.
This is preventing us from generating artifacts for the remaining tables, which have the correct referential integrity. We could have avoided this by deselecting the tables that had the issues.
Regards.