|
Kathey Marsden wrote: Right... AM was for Abstract Machine. The ideas was to isolate JDBC implementation from actual protocol code. It may be possible to implement NET package to use underlying embed JDBC code, so both embedded and client JDBC drivers could share AM code. But I hope I didn't re-ignite David's pet project of sharing code between client and embed drivers. :-) While it is a good idea, I think underlying code sharing issues need to be resolved first, in my opinion.David W. Van Couvering wrote: Satheesh |
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 specific B... Satheesh Bandaram
- Re: [jira] Updated: (DERBY-796) jdbc 4.0 speci... David W. Van Couvering
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
- [jira] Updated: (DERBY-796) jdbc 4.0 specific ... V.Narayanan (JIRA)
