| Summary: | TestConnection from DD Editor's Resource Binding page | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Zhi Zhu <zhuzhi> |
| Component: | EDT | Assignee: | Zhi Zhu <zhuzhi> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chenzhh, smythew, tdramsey, tww |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Zhi Zhu
Based on a past conversation with Tim, we are no longer going to limit the databases that can be used by an EGL application. Assuming it supports standard JDBC operations, it should be allowed. It is up to the developer to write any custom SQL for cases when the SQL we use for specific statements does not work. For the 'ResourceBinding' page to show SQL database binding messages, I suggest to save the following fields to *.egldd file 1> name: the id of the item in all sql database binding list, default to dbVerdor+" "+dbVersion 2>dbms(SQL Database): default to dbVerdor+" "+dbVersion 3>dbProfileID: is used in TestConnection to distinguish different DB, is also used in dropdown list to select list, the field should not be changed by user and can select to not display it on user interface. 4>JDBC driver class 5>connection url 6>JNDI name 7>databse name 8>user name 9>password 10>Default schema: the field seems useless and cannot be applied to all database, so I suggest removing it How about your opinion about this? fix it close it |