db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1015) Define interface between network server and engine through Java interfaces.
Date Tue, 20 Mar 2007 23:39:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel John Debrunner closed DERBY-1015.
----------------------------------------


> Define interface between network server and engine through Java interfaces.
> ---------------------------------------------------------------------------
>
>                 Key: DERBY-1015
>                 URL: https://issues.apache.org/jira/browse/DERBY-1015
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>             Fix For: 10.2.1.6
>
>         Attachments: derby1015.diff.txt, Derby1015.p2.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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message