[dtp-dev] SQL Dev Tools contribution: M3 Iteration1 -- SQL Editor Framew

[Hui.Cao@xxxxxxxxxx]

Hi,
        We've
delivered the M3 1st iteration of SQL Editor Framework & SQL Debugger
Framework into the datatools CVS repository. 

Contents include:

• org.eclipse.datatools.sqltools.sqleditor plugin :

  Added "Database Development" perspective;
        Added
sql statement execution code calling results view API; (can not run for
now, see limitations below)
        Added
content assist feature by extracting information from the parsing result
of a SQLParser, which is contributed through the "org.eclipse.datatools.sqltools.db.generic.dbFactory"
extension point;
        Added
customizable syntax highlighting: now different databases can have their
own syntax highlighting rule by contributing a "ISQLSyntax" instance
through the "org.eclipse.datatools.sqltools.db.generic.dbFactory"
extension point;

• org.eclipse.datatools.sqltools.routineeditor plugin (NEW):

  Added SQL Routine editor support including routine editor
input, routine editor document provider, routine execution code, routine
parameter configuration code, routine launch configuration code, and a
"documentprovider" extension point for debugger plugin to extend.
Although nearly all the required classes are there, routine editor can
not run for now, see limitations below.

• org.eclipse.datatools.sqltools.db.generic plugin (NEW):

  A generic SQL parser written in JavaCC supporting generic
SQL query statements;
        Contributes
to "org.eclipse.datatools.sqltools.db.generic.dbFactory"
extension point

• org.eclipse.datatools.sqltools.db.generic.test plugin (NEW):

  Test cases for the generic SQL parser.

• org.eclipse.datatools.sqltools.db.derby plugin (NEW):

  A preliminary implementation for Derby database support.

• org.eclipse.datatools.sqltools.debugger.core plugin :

  Most of the SQL debugger framework codes were checked in,
including breakpoint verification, breakpoint management actions, launch
configuration in debug mode, extension to the routine editor (document
provider, text hover), source lookup, and a "Database Debug"
perspective.

• org.eclipse.datatools.sqltools.sql plugin:

      Added visitor support in the AST classes;

• org.eclipse.datatools.sqltools.editor.core plugin :

  Added more methods in ProfileUtil to integrate with Connectivity
layer

• org.eclipse.datatools.sqltools.common.ui plugin:

Added several utility classes

Limitations:
IConnectionProfile.createConnection
will cause IllegalStateException when called more than once, therefore
the "Set Connection Info" dialog in scrapbook editor does not
work well and we can not execute sql statements or launch routines in the
editor;
I haven't figured out how to get the
sql model objects instantiated by connectivity layer, so the routine editor
can not work now.
I have raised the above 2 problems in
DTP bugzilla: 
122905:Get SQL model objects from connectivity
layer for SQL Dev Tools
114400:Enhance Connection Management
(Added comments)

Plans for next week:
Workable routine editor (depends on
the resolving of the above mentioned limitations)
- Life cycle management (C ) [SM, Conn]
- Routine launch configuration - run mode ( C) [SM,
Conn, DDM]
- code template (H)
- syntax validation (H)
- Outline view (H)
- statement execution
Integration w/ Model Base and Connectivity



Best Regards!

Hui Cao

DTP SQL Dev Tools Committer, Workgroup
Lead
Sr S/W Eng - Dev
Sybase, Inc. Shanghai, China