-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 
Author Message
 Post subject: Regarding selective reverse engineering of tables
PostPosted: Mon Mar 14, 2005 2:06 pm 
Newbie

Joined: Fri Feb 04, 2005 11:09 pm
Posts: 9
Hello,
With the alpha 1 release of tools, is it possible to do selective reverse engineering of tables instead of the entire schema.

We have a large number of tables, and need to incremently select a few that have changed instead of the entire schema.

Regards.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Mar 14, 2005 4:11 pm 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
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.)

_________________
Max
Don't forget to rate


Top
 Profile  
 
 Post subject: Regarding selective reverse engineering of tables
PostPosted: Mon Mar 14, 2005 9:03 pm 
Newbie

Joined: Fri Feb 04, 2005 11:09 pm
Posts: 9
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.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Mar 15, 2005 2:42 am 
Hibernate Team
Hibernate Team

Joined: Tue Aug 26, 2003 6:10 am
Posts: 8615
Location: Neuchatel, Switzerland (Danish)
we plan to add so tables without primary key will be handled by using all the columns as the id.

alpha 3 is in the 1-2 month time frame. alpha 2 will be out soon.

_________________
Max
Don't forget to rate


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.