Bug 146451 - Detect existing entities when generating new entities from schema
Summary: Detect existing entities when generating new entities from schema
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-06-11 19:35 EDT by Gunnar Wagenknecht CLA
Modified: 2011-07-01 16:24 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2006-06-11 19:35:39 EDT
Usually, when you migrate a project you do it step-by-step. When generating entities from an existing schema this approach is not supported by Daily because relations are only resolved against new tabled in the generation scope.

Existing entities in the project should be recognized, too, when generating new entities from existing tables. This would better fit an incremental development/migration approach. Relations would be resolved against existing entities and as a benifit the existing entities would get new fields/methods, too, if a new relation to an already existing entity is detected.
Comment 1 Brian Vosburgh CLA 2006-06-22 16:59:18 EDT
This makes more sense now that we have reworked the wizard to allow the user to preview the Entity names. Previously it did not make sense, since the generation of Entity names is not entirely deterministic.

We need to move some code from GenTable to GenerateEntitiesWizardPage so that name collisions are handled and displayed to the user. We also need to prevent the user from entering duplicate entity names.
Comment 2 Gunnar Wagenknecht CLA 2006-06-22 17:20:12 EDT
Sounds great. :)
Comment 3 Neil Hauge CLA 2007-07-30 13:48:24 EDT
Investigate for 2.0.
Comment 4 Neil Hauge CLA 2008-02-29 11:24:01 EST
It's not looking like this will make the 2.0 release, since we haven't managed to investigate further at this point, and it is a non-trivial enhancement.  Setting to future to be evaluated for 3.0.
Comment 5 Neil Hauge CLA 2011-07-01 16:24:56 EDT
Moving JPA specific bugs to new JPA component in bugzilla.