[dtp-dev] Re: Fw: Exemplary Derby Routine Editor first version is pendin

[Der Ping Chou <dpchou@xxxxxxxxxx>]

Hui,

Appreciated that you pointed out this
is generic to all major database vendor. It is actually a preferable approach
to add this into SQLModel if they fall into this category. Just curious
to know if this also part of the SQL 99 or 2003 specification that we missed.

Have you have a chance to verify the
code that were checked in so far?

Thanks,

Der-Ping Chou
Information Management Tooling
Development Manager - Data Tools
Seattle IBM Office
tel : 1-206-587-5946 (T/L: 277-5946)

Hui.Cao@xxxxxxxxxx

02/27/2006 06:34 PM

To	Der Ping Chou/Redmond/IBM@IBMUS, dtp-dev@xxxxxxxxxxx
cc
Subject	Re: Fw: Exemplary Derby Routine Editor first version is pending to commit

Thanks Der Ping, 
        I've just create a new bug for the SQLModel
part: bug129706: "Extend SQLModel: Event and Routine.sourceVisible".
        I think deriving a new specialized Derby model
from SQLModel is a great idea. This extension mechanism will be very useful.
But for this bug, We expect them to be added into the base model instead
of into a separate derived model since they look generic to all databases.
In this way, SQL Editor Framework can depend on them.

Best Regards!

Max ( Hui ) Cao
DTP SQL Dev Tools Committer
Sr S/W Eng - Dev
Sybase, Inc. Shanghai, China

Der Ping Chou <dpchou@xxxxxxxxxx>

02/28/2006 09:43 AM

To	Hui.Cao@xxxxxxxxxx
cc	dtp-dev@xxxxxxxxxxx, dtp-pmc@xxxxxxxxxxx, Hemant S Kolwalkar <hskolwal@xxxxxxxxxx>
Subject	Re: Fw: Exemplary Derby Routine Editor first version is pending to commit

Hui, 

We just checked in the changes for dbdefinition model and also updated
the API. In order to stream line the changes, we have updated the UML model
and regenerate the ecore model. Here are the snapshot of the changes:

• A new DebuggerDefinition class is added
• Attributes (eventSupported, sqlUDFSupported and, storedProcedureSupported) are added in Database VendorDefinition class.
• Did not add the request for trigger attribute, since it already exists.
• org.eclipse.datatools.connectivity.sqm.core\src\org\eclipse\datatools\connectivity\sqm\internal\core\definition package is also changed to consume the new dbdefinition model.

As I mentioned in my previous e-mail, please file a new defect for SQLModel
related change. Most likely we will come up with a specialized model for
Derby. 

Thanks, 

Der-Ping Chou
Information Management Tooling
Development Manager - Data Tools
Seattle IBM Office
tel : 1-206-587-5946 (T/L: 277-5946)

Hui.Cao@xxxxxxxxxx

02/20/2006 01:20 AM

To	Der Ping Chou/Redmond/IBM@IBMUS
cc	dtp-dev@xxxxxxxxxxx
Subject	Fw: Exemplary Derby Routine Editor first version is pending to commit

Hi Der Ping, 
      Could you please have a look at the Bug 109112: "Needs
new attributes (sqlUdfSupported, eventSupported) and class (DebuggerDefinition)"
? I had modified my SQL Dev Tools code based on the patches I uploaded
for the Bug. Without this fix, I can not proceed. Thanks!

Best Regards!

Max ( Hui ) Cao
DTP SQL Dev Tools Committer
Sr S/W Eng - Dev
Sybase, Inc. Shanghai, China

----- Forwarded by Hui Cao/SYBASE on 02/20/2006 04:54 PM -----

Hui Cao/SYBASE

02/17/2006 09:50 PM

To	dtp-dev@xxxxxxxxxxx
cc
Subject	Exemplary Derby Routine Editor first version is pending to commit

Hi, 
      I was about to commit the exemplary derby routine
editor when I found that this feature relies on some modified model base
and connectivity code and this checkin would break the build. I've created/updated
bug entries for the prerequisite tasks: 
Bug 109112: "Needs new attributes (sqlUdfSupported, eventSupported)
and class (DebuggerDefinition)" (I've uploaded the patches)
Bug 128396: "ManagedConnection.isConnected() returns wrong value"

      Once the above mentioned bugs have been fixed, I'll
proceed with the commit. This feature is still at its crude stage, only
being able to show the source code for Derby Trigger. Detailed information
can be found in Bug 128392: "Routine.getSource() returns null".
As to the "save" function, I expect it can be accomplished in
Bug 128394 by connectivity layer: "Lack of means to persist the Routine
object back to database". But I'm always glad to discuss it with anyone
who don't think so. Thanks! 

Best Regards!

Max ( Hui ) Cao
DTP SQL Dev Tools Committer
Sr S/W Eng - Dev
Sybase, Inc. Shanghai, China