db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Boynes <jboy...@apache.org>
Subject Re: [VOTE] Network client driver should match embedded where possible for implementation specific behaviour.
Date Mon, 23 May 2005 21:44:27 GMT
Kathey Marsden wrote:
> Satheesh filed DERBY-310 to manage this issue, but to clarify
> direction,  I thought it worthwhile to submit this to vote:
> 
> There are some differences in behaviour when using the  client  vs the
> embedded driver.  Examples are DERBY-211 and DERBY-254. Other
> differences are not logged as JIRA entries but are evidenced by
> differences in test output.  To create a seamless transition from
> embedded to client, the client driver should be changed to match
> embedded where possible.
> 
> [  ] Change Network Client/Server behaviour to match embedded where
> possible.
> 
> 
> 

+1 with a couple of questions

What are people's opinions on unification?

What about features (like trace) that the client has but embedded 
doesn't? Should they be backported to the embedded driver?

--
Jeremy



Mime
View raw message