I think there could be three different pieces to this:
(1) SQL rendering
(2) JDBC wrappers
(3) A metamodel for relational data
Currently, Hibernate has classes for rendering things like inserts,
updates,
selects, outer joins, case where, in, etc in the .sql package. However, the
APIs here are prob
Steve Ebersole; [EMAIL PROTECTED]
Subject: RE: [Hibernate] simple persistence solution needed
Very low level of abstraction for now, i.e. setting parameters, reading
result sets, table creation using abstract data types.
What branch should I check out for this?
> -Original Message-
>
y Loubyansky; [EMAIL PROTECTED]
> Subject: RE: [Hibernate] simple persistence solution needed
>
> Have not seen a response, so I'll take a stab...
>
> I think it would depend upon the type of abstraction you are
> looking for here. The abstractions of the db structure
subselects and
accounting for the various dialects during rendering.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexey
Loubyansky
Sent: Wednesday, September 22, 2004 7:26 AM
To: [EMAIL PROTECTED]
Subject: [Hibernate] simple persistence solution needed
Hello colleagues,
there are areas in JBoss that need persistence solutions. Right now each
area has its own more or less ugly solution (not because of developers'
skills but more because of JDBC portability issues, differences in
database data types, etc). We could use Hibernate. But Hibernate is
