Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Jdbc > Non-ORM layers ...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 10 Topic 1905 of 1984
Post > Topic >>

Non-ORM layers over JDBC

by craig@[EMAIL PROTECTED] (Craig Ringer) Mar 24, 2008 at 02:45 PM

Hi all

I'm fairly new to Java (sorry!) and struggling with the database access 
area. My PostgreSQL database is fairy complex and significant parts of 
its user interface are through stored procedures etc. I've been looking 
into Hibernate / Hibernate EntityManager and other EJB3-compatible 
tools, but they all seem to be oriented toward database-independence and 
using the DB as a dumb storage engine. They even implement their own 
outer joins (!) and other core DB functionality. Currently I'm trying to 
figure out why a "SELECT c FROM customer c;" (Hibernate-style) is 
introducing a WHERE clause for on the customer's bank_id when executed 
.... so I'm not impressed so far.

However, I've also looked at raw JDBC code, and it seems to be very 
verbose with a lot of manual data conversion and little language 
integration.

I'm somewhat spoiled by having come from C++ with TrollTech's Qt, a 
toolkit so good that it makes C++ not only worth using but even nice. It 
has SQL-enabled widgets with a lot of programmer control, and a very 
nice and well integrated SQL interface that doesn't impose too many 
weird limits or force you to work around your SQL access layer to do 
simple things. It makes good use of variant types and conversion 
operators to minimise the amount of manual type wrangling the programmer 
has to do.

I've done a fair bit of searching but haven't found any sort of JDBC 
over-layer that integrates database access into the Java language a bit 
better but without all the ORM database-independence stuff.

What do people here use? Just use the JDBC directly? Use an ORM layer 
even though you just target PostgreSQL and work around its limitations 
and quirks? Use a different ORM layer without weird limitations and 
quirks? Some other tool I haven't been able to find out about?

I'm writing a pretty ordinary desktop app, but I was really hoping to 
avoid writing vast amounts of database interface code even for the 
simpler parts of the interface, as appears to be necessary with direct 
JDBC use.

Comments on what you're using or would like to have used would be very 
much appreciated.

--
Craig Ringer

-
Sent via pgsql-jdbc mailing list (pgsql-jdbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc




 10 Posts in Topic:
Non-ORM layers over JDBC
craig@[EMAIL PROTECTED]   2008-03-24 14:45:05 
Re: Non-ORM layers over JDBC
davidclark@[EMAIL PROTECT  2008-03-24 09:53:11 
Re: Non-ORM layers over JDBC
craig@[EMAIL PROTECTED]   2008-03-25 02:40:55 
Re: Non-ORM layers over JDBC
pg@[EMAIL PROTECTED] (Da  2008-03-24 22:18:59 
Re: Non-ORM layers over JDBC
Stephen.Denne@[EMAIL PROT  2008-03-25 09:57:24 
Re: Non-ORM layers over JDBC
craig@[EMAIL PROTECTED]   2008-03-25 10:01:26 
Re: Non-ORM layers over JDBC
petite.abeille@[EMAIL PRO  2008-03-26 20:28:12 
Re: Non-ORM layers over JDBC
halset@[EMAIL PROTECTED]   2008-03-26 11:21:45 
Re: Non-ORM layers over JDBC
petite.abeille@[EMAIL PRO  2008-03-26 20:48:10 
Re: Non-ORM layers over JDBC
mark.lewis@[EMAIL PROTECT  2008-03-26 08:15:54 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Fri Jul 4 9:16:29 CDT 2008.