Refactoring of JDBC-based storage engines

[GoogleCodeExporter]

Refactoring of storage engine to share a same codebase for all RDBMS based
storage engines will help generalizing code for adding new backends,
simplify maintenance and building tools on top of them. 

Also, this will cover implementation of following backends on top of it:
1) MySQL
2) HSQLDB
3) PostgreSQL

Original issue reported on code.google.com by igor%vas...@gtempaccount.com on 4 Feb 2009 at 12:32

[GoogleCodeExporter]

Original comment by jay.kr...@gmail.com on 11 Feb 2009 at 6:06

• Changed title: Refactoring of JDBC-based storage engines

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

implementation without mysql wrapper

Original comment by cab...@gmail.com on 12 Feb 2009 at 8:00

Attachments:

• jdbc_patch.diff.gz

[GoogleCodeExporter]

Original comment by ismaelj on 21 Sep 2009 at 8:12

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

What's the status on this issue? The patch doesn't appear to merge cleanly. 

Guys - if it's worth the effort, I can take a look at this one.

Thanks.

Original comment by kirktrue.im@gmail.com on 17 Feb 2010 at 4:34

[GoogleCodeExporter]

We are working on improving the performance of the MySQL store.  Please assign 
this
one to me.

Original comment by mramb...@gmail.com on 17 Feb 2010 at 5:22

[GoogleCodeExporter]

Original comment by jay.kr...@gmail.com on 20 Feb 2010 at 3:03

[GoogleCodeExporter]

mrambach: are you guys both improving mysql performance and creating a generic 
JDBC 
storage engine?

Original comment by krum...@gmail.com on 9 Mar 2010 at 8:30

[GoogleCodeExporter]

Mark, are you working on this?

Original comment by kirktrue.im@gmail.com on 18 Nov 2010 at 6:49