Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356461 - Expose select SQL preferences within Record from SQL Database wizard
Summary: Expose select SQL preferences within Record from SQL Database wizard
Status: NEW
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-09-01 08:24 EDT by Will Smythe CLA
Modified: 2017-02-23 14:18 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Will Smythe CLA 2011-09-01 08:24:11 EDT 
Some of the settings under Preferences > EGL > SQL (see bug 355909) are used to map database column types to EGL types as well as to transform the column name into a 'better' field name. These settings should be exposed in the Record from SQL Database wizard so the developer can easily alter these mappings on a case-by-case basis.

I am opening this as a placeholder ... we should discuss in more detail when it comes time to do this one.
Comment 1 Zhi Zhu CLA 2011-09-02 02:16:33 EDT 
Will:
  Do you mean adding a similar property page as the preference page during record creation process (from Sql database)?
Comment 2 Tony Chen CLA 2011-12-28 02:36:18 EST 
What about giving a link to the preference page. 

Thought that user would like consistent settings when they create Entity Records multiple times (after altering a column or adding a column). If the setting can be specified in the wizard each time the wizard runs, and with out the ability to be saved, user could hurt himself. Think about the scenario that you create entity record 10 days ago with lower case names, now you are creating the entity record again because some new columns are added, the default naming is used because you forgot to check "change to lower case". Then the record created simply don't work with existing code. It's not a big deal to fix, but we can avoid this.
Comment 3 Will Smythe CLA 2011-12-28 07:46:00 EST 
I like the idea of a link to the preference page.