JDBC Producer

[GoogleCodeExporter]

Include a producer implementation as part of the odata4j distribution backed by 
jdbc only - i.e. expose db entities (tables,views,sps) directly as odata 
entities without the additional layer of JPA.

Although one could argue this goes against the spirit of the odata entity 
model, it would be extremely useful for very simple database models and lower 
the barrier of entry for some.

Original issue reported on code.google.com by john.spurlock on 8 Mar 2011 at 3:58

[GoogleCodeExporter]

SQL Server 2000 R4 / jtds-1.2.4
SQL Server 2008 R2 / jtds-1.2.4
Oracle 11g 11.1.0.1.0 / ojdbc6
H2 1.3 / org.h2.Driver 1.3

Original comment by john.spurlock on 18 Dec 2011 at 6:01

• Changed state: Started
• Added labels: Milestone-Release0.6

[GoogleCodeExporter]

Original comment by john.spurlock on 1 Mar 2012 at 1:10

• Added labels: Milestone-Release0.7
• Removed labels: Milestone-Release0.6

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi John,

I see this feature is for Milestone 0.7, is it still on schedule?

Original comment by jose.cha...@gmail.com on 16 Jun 2012 at 2:02

[GoogleCodeExporter]

Original comment by john.spurlock on 9 Jul 2012 at 12:09

• Added labels: Milestone-Release1.0
• Removed labels: Milestone-Release0.7

[GoogleCodeExporter]

Hi John,

is there something started already on that feature? I was about to start doing 
something like that when I saw that mention on the roadmap... if this i still 
on the agenda maybe we could help in getting implementing instead of starting 
from scratch.

Regards,
Marian

Original comment by marian....@gmail.com on 27 Jul 2013 at 5:22

[GoogleCodeExporter]

I technically have in development a working JDBC producer that implements full 
CRUD, $skip, $top, $count. Would be interested in contributing them back to 
odata4j. just let me know.

cheers

Original comment by chard...@gmail.com on 4 Nov 2013 at 5:53