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] Updated: (DERBY-1015) Define interface between network server and engine through Java interfaces.
Date Mon, 10 Jul 2006 19:19:32 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1015?page=all ]

Sunitha Kambhampati updated DERBY-1015:

    Attachment: Derby1015.p2.diff.txt

I am attaching a phase 2 patch ( derby1015.p2.diff.txt, derby1015.p2.stat.txt)  to address
adding the new interface for ResultSet.  

This patch derby1015.p2.diff.txt  can be applied independently of the derby1015.diff.txt.

The changes in this patch include
-- add a new interface EngineResultSet  for use in Network Server
--  make changes in network server code to make use of this interface instead of EmbedResultSet.

Ran derbyall on linux/ibm142 OK on linux. 

Can someone please review this patch.  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:
>  Attachments: Derby1015.p2.diff.txt, derby1015.diff.txt, derby1015.p2.stat.txt, derby1015.stat.txt
> 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:
For more information on JIRA, see:

View raw message