Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355785 - Support generation of entity records per EDT SQL Access spec
Summary: Support generation of entity records per EDT SQL Access spec
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Zhi Zhu CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-24 23:03 EDT by Will Smythe CLA
Modified: 2017-02-23 14:15 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Smythe CLA 2011-08-24 23:03:23 EDT
Developers should be able to create entity records by selecting 1 or more tables for a database connection defined in the workspace. This function should be exposed via the EGL New Record wizard.
Comment 1 Will Smythe CLA 2011-08-24 23:16:55 EDT
Checked code in CVS under this bug. Known issues:

1) Strings in the new SQL wizard and page have not been NLSed -- need to be added to appropriate properties files. Same is true for new part template defined in plugin.xml of edt.ide.ui.

2) eglx.persistence.sql import statement needs to be added to new record file(s). Not sure where in the code this should be done -- doesn't seem correct to do in the wizard. Should be part of the generator that takes DataTools objects and produces EGL source.

3) Not all column annotation fields in the 0.1 spec are being handled (e.g. insertable , updateable).

4) Wizard does not nicely handle situation where an improperly configured database connection is selected in the Database Tables page. For example, if the password is not specified in the connection settings, selecting the connection from the drop-down results in a Problem occurred dialog being displayed. We really should open the Connection configuration dialog for the connection.

5) "Qualify tables names with schema" checkbox has no effect. Do we still need this? Think so.

6) "Save data source to DD" checkbox has no effect. This will need to be implemented once the design for data sources is finalized.

7) Preferences for how db columns are mapped to EGL types and how column names are formatted are not being honored (see EGLSQLRetrieveUtility.setItemNameControlOptionsBasedOnSQLPreferences)
Comment 2 Tony Chen CLA 2011-08-29 01:45:30 EDT
Will, you are still the owner of this enhancement, would you like to continue working on it or assign the coding work to ZhuZhi while you still work on the design and requirement.
Comment 3 Will Smythe CLA 2011-09-01 08:29:25 EDT
Assign to ZhuZhi.
Comment 4 Zhi Zhu CLA 2011-09-06 01:08:42 EDT
Implement 1,3,4,5,6,7; for Item 2, need underlying implementation.

BindingSQLDatabaseConfiguration
EGLDDBindingWizard

SQLDatabaseBindingWizardPage

EGLDDBindingConfiguration

BindingSQLDatabaseConfiguration

ServiceBindingWizardPage

EGLDDRootHelper


RecordFromSqlDatabaseWizard  --- add much

ServiceOperation ---getEGLDDFileHandle()

DBModelingUtil.getDefinition()

EGLSQLRetrieveUtility.populateStructureItem
EGLSQLRetrieveUtility.resolveToEGLType
Comment 5 Zhi Zhu CLA 2011-09-06 05:57:22 EDT
fix it
Comment 6 Zhi Zhu CLA 2011-10-13 00:32:18 EDT
close it