Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dtp-dev] SQL Dev Tools contribution: M3 Iteration1 -- SQL Editor Framework & SQL Debugger Framework

There's a couple of things to note about the recent SQL Dev Tools
deliveries:

(1) The "...plan" plug-in adds a dependency to GEF. We will now need to
track GEF builds, in addition to EMF and platform ones, as part of
synchronization during Callisto. As with EMF and the platform, this levies
the requirement on component owners using this to keep updated with respect
to GEF builds for the release train.

(2) Two plug-ins, org.eclipse.datatools.sqltools.editor.core and
org.eclipse.datatools.sqltools.result, contain code
(org.eclipse.runtime.Assert) that is Eclipse 3.2 dependent. Let me
emphasize again here that DTP through (at least) version 1.0 will be
developed on Eclipse 3.1 and tested against Eclipse 3.2. All code must
build in Eclipse 3.1; any code that is Eclipse 3.2 specific can not be
used.

I've updated the two plug-ins in CVS under Bugzilla 122924 to remove these
Eclipse 3.2 dependencies for today's iteration build. As we move toward an
automated build system (hence less user iteration during the build
process), such errors will result in exclusion of a plug-in from a given
build and, if there are downstream dependencies on the excluded plug-in, a
broken build. Therefore each committer needs to exercise appropriate
attention to all code deliveries.

Regards,
John Graham
Eclipse Data Tools Platform PMC
Staff Software Engineer
Sybase, Inc.



                                                                           
             Hui.Cao@xxxxxxxxx                                             
             m                                                             
             Sent by:                                                   To 
             dtp-dev-bounces@e         dtp-dev@xxxxxxxxxxx                 
             clipse.org                                                 cc 
                                                                           
                                                                   Subject 
             01/06/2006 10:51          [dtp-dev] SQL Dev Tools             
             AM                        contribution: M3 Iteration1 -- SQL  
                                       Editor Framework & SQL Debugger     
                                       Framework                           
             Please respond to                                             
              DTP development                                              
               mailing list                                                
             <dtp-dev@eclipse.                                             
                   org>                                                    
                                                                           
                                                                           





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_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev




Back to the top