db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1015) Define interface between network server and engine through Java interfaces.
Date Tue, 23 May 2006 00:32:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1015?page=comments#action_12412847 ] 

Sunitha Kambhampati commented on DERBY-1015:
--------------------------------------------

I am proposing the following interface for the EnginePreparedStatement for use in the network
server. 

snippet:

+public interface EnginePreparedStatement extends PreparedStatement {
+ 
+ /**
+  * Immitate the function in JDBC 3.0
+  *
+  * Retrieves the number, types and properties of this PreparedStatement
+  * object's parameters.
+  *
+  * @return a EmbedParameterSetMetaData object that contains information about the
+  * number, types and properties of this PreparedStatement object's parameters.
+  * @exception SQLException if a database access error occurs
+    */
+    public EmbedParameterSetMetaData getEmbedParameterSetMetaData()
+    throws SQLException;
+    
+    
+}

EmbedPreparedStatement implements EnginePreparedStatement
BrokeredPreparedStatement implements EnginePreparedStatement

Thoughts/comments ?   Thanks.

> Define interface between network server and engine through Java interfaces.
> ---------------------------------------------------------------------------
>
>          Key: DERBY-1015
>          URL: http://issues.apache.org/jira/browse/DERBY-1015
>      Project: Derby
>         Type: Improvement

>   Components: JDBC
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner
>      Fix For: 10.2.0.0

>
> API between the network server and engine is not well defined, leading to inconsistent
& multiple ways of handling the different objects returned, such as reflection, explicit
casting etc. This in turn has lead to bugs such as DERBY-966 . DERBY-1005, and DERBY-1006,
and access to underlying objects by the application that should be hidden.
> Define interfaces, such as EngineConnection, that both EmbedConnection and BrokeredConnection
implement. Thus the network server can rely on the fact that any connection it obtains will
implement EngineConnection, and call the required methods through that interface.
> Most likely will need EngineConnection, EnginePreparedStatement and EngineResultSet..
These interfaces would be internal to derby and not exposed to applications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message