| [Teneo] Should we use Hibernate or JDO? [message #64909] |
Tue, 19 December 2006 10:44  |
Eclipse User |
|
|
|
We've just started looking into persisting our EMF models to a database,
and we've decided to go with Teneo for this purpose. We've already got
Hibernate set up for a different (non-EMF related) part of our application,
so if Hibernate and JDO were equally well supported, we'd probably go with
Hibernate. However, some of the documents we've seen seem to imply that
Teneo has better support for JDO, in particular with respect to lazy loading
and multiple interface inheritance.
Since we haven't started writing any Teneo-related code yet, we were
wondering if someone who were starting from scratch should favour JDO over
Hibernate or not. Is there a webpage or some other document comparing the
pros and cons of each?
- Oliver
|
|
|
| Re: [Teneo] Should we use Hibernate or JDO? [message #64928 is a reply to message #64909] |
Tue, 19 December 2006 14:22  |
| Eclipse User |
|
|
|
Hi Oliver,
There is no document comparing the pros or cons.
JPOX/jdo has better support for lazy loading for single associations (and fetch groups). Both jpox
and hibernate support lazy loading of lists. Also Hibernate Teneo has much better support for
different jpa annotations (and hibernate specific annotations). Dynamic emf works with hibernate but
not with jpox.
Overall I would advice anyone familiar with jdo to stay with jpox and familiar with hibernate to use
hibernate. I myself use hibernate because I find the compile time class enhancement (which is needed
for jpox) less practical, but this is my personal way of working.
So if you are already using hibernate then I would stick to that. If you find any issues with
hibernate or missing functionality then please report it and we will do our best to adapt Teneo.
gr. Martin
Oliver Wong wrote:
> We've just started looking into persisting our EMF models to a database,
> and we've decided to go with Teneo for this purpose. We've already got
> Hibernate set up for a different (non-EMF related) part of our application,
> so if Hibernate and JDO were equally well supported, we'd probably go with
> Hibernate. However, some of the documents we've seen seem to imply that
> Teneo has better support for JDO, in particular with respect to lazy loading
> and multiple interface inheritance.
>
> Since we haven't started writing any Teneo-related code yet, we were
> wondering if someone who were starting from scratch should favour JDO over
> Hibernate or not. Is there a webpage or some other document comparing the
> pros and cons of each?
>
> - Oliver
>
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Should we use Hibernate or JDO? [message #65196 is a reply to message #64928] |
Wed, 20 December 2006 09:46 |
| Eclipse User |
|
|
|
"Martin Taal" <mtaal@elver.org> wrote in message
news:em9e5t$5r0$1@utils.eclipse.org...
>
> Overall I would advice anyone familiar with jdo to stay with jpox and
> familiar with hibernate to use hibernate. I myself use hibernate because I
> find the compile time class enhancement (which is needed for jpox) less
> practical, but this is my personal way of working.
> So if you are already using hibernate then I would stick to that. If you
> find any issues with hibernate or missing functionality then please report
> it and we will do our best to adapt Teneo.
Okay, thanks Martin. We'll probably stick with Hibernate then.
- Oliver
|
|
|
| Re: [Teneo] Should we use Hibernate or JDO? [message #597108 is a reply to message #64909] |
Tue, 19 December 2006 14:22 |
| Eclipse User |
|
|
|
Hi Oliver,
There is no document comparing the pros or cons.
JPOX/jdo has better support for lazy loading for single associations (and fetch groups). Both jpox
and hibernate support lazy loading of lists. Also Hibernate Teneo has much better support for
different jpa annotations (and hibernate specific annotations). Dynamic emf works with hibernate but
not with jpox.
Overall I would advice anyone familiar with jdo to stay with jpox and familiar with hibernate to use
hibernate. I myself use hibernate because I find the compile time class enhancement (which is needed
for jpox) less practical, but this is my personal way of working.
So if you are already using hibernate then I would stick to that. If you find any issues with
hibernate or missing functionality then please report it and we will do our best to adapt Teneo.
gr. Martin
Oliver Wong wrote:
> We've just started looking into persisting our EMF models to a database,
> and we've decided to go with Teneo for this purpose. We've already got
> Hibernate set up for a different (non-EMF related) part of our application,
> so if Hibernate and JDO were equally well supported, we'd probably go with
> Hibernate. However, some of the documents we've seen seem to imply that
> Teneo has better support for JDO, in particular with respect to lazy loading
> and multiple interface inheritance.
>
> Since we haven't started writing any Teneo-related code yet, we were
> wondering if someone who were starting from scratch should favour JDO over
> Hibernate or not. Is there a webpage or some other document comparing the
> pros and cons of each?
>
> - Oliver
>
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Should we use Hibernate or JDO? [message #597226 is a reply to message #64928] |
Wed, 20 December 2006 09:46 |
| Eclipse User |
|
|
|
"Martin Taal" <mtaal@elver.org> wrote in message
news:em9e5t$5r0$1@utils.eclipse.org...
>
> Overall I would advice anyone familiar with jdo to stay with jpox and
> familiar with hibernate to use hibernate. I myself use hibernate because I
> find the compile time class enhancement (which is needed for jpox) less
> practical, but this is my personal way of working.
> So if you are already using hibernate then I would stick to that. If you
> find any issues with hibernate or missing functionality then please report
> it and we will do our best to adapt Teneo.
Okay, thanks Martin. We'll probably stick with Hibernate then.
- Oliver
|
|
|
Powered by
FUDForum. Page generated in 0.03470 seconds
Home