Thank you! $kala. ----- Original Message ----- From: "Thomas Mahler" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, October 11, 2002 7:22 PM Subject: Re: Persistence broker vs. ODMG vs. JDO with OJB
> Hi, > > The faq.html gives some hints on when to use which API. > here are some more arguments: > > JDO > contra: > - We have a JDO prototype, but I can't recommend it for production use. > It's simply not finished. > > ODMG > pro: > - provides you with a full fledged object level transaction (i.e. unit > of work) concept. > - it hides a lot of persistence details from the application developer > - it's a standard API > - you can mix OJB ODMG code seemlessly with PersistenceBroker code (for > performance critical stuff or for Queries) > > contra: > - It's introducing much overhead and is thus not as fast as the > PersistenceBroker API > > > PersistenceBroker: > pro: > - lean and mean, PB is minimum overhead, and thus the fastest OJB API. > - provides maximum coding flexibility, you can even access the > underlying JDBC connections if necessary > - The query API is a real OO solution. we have a nice abtract syntax > tree representation of query expression. ODMG OQL and JDOQL are String > based query APIs. Many OJB users are thus using PB queries even inside > their OJB ODMG applications > > contra: > - its a kernel API and does not provide all comfort you can expect from > JDO or ODMG. For example the user is responsible to track if items have > been deleted from collections and to delete these items explicitely from > the database. The ODMG implementation can handle this implicitely > without extra coding. > - PB does not provide object level transaction but uses jdbc > transactions, so the user has to take care to keep PB transactions open > only a short time to save db resources. ODMG transactions can remain > open for months without problems. > > Marian Skalsky wrote: > > Hi there! > > > > I'm a newbie in OJB and I've got, aka old chestnut question, but I was > > unable to find the answer on the mailing list archive. > > I need some persistent layer for my future web project based on struts. From > > these (Torque, Hybernate and OJB) I decided for OJB. > > Now I think about which API to choose. As I worked a bit with EJB before > > (but it is too robust for this project) I lean towards to use of JDO API. > > JDO seems to me to be very close to EJB and concerning to discussion at > > http://www2.theserverside.com/discussion/thread.jsp?thread_id=771#57149 I > > think it should fit my needs. > > > > And what I wanna ask: > > Can somebody experienced name advantages and disadvantages of each API > > aproach (Persistence broker, ODMG, JDO) (or provide the link where to find > > answers)? > > > > I will appreciate it very much! > > Thx in advance. > > > > $kala. > > > > > > --- > > Odch?dzaj?ca spr?va neobsahuje v?rusy. > > Skontrolovan? antiv?rusov?m syst?mom AVG (http://www.grisoft.cz). > > Verzia: 6.0.394 / V?rusov? datab?za: 224 - d?tum vydania: 4. 10. 2002 > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > --- Odch?dzaj?ca spr?va neobsahuje v?rusy. Skontrolovan? antiv?rusov?m syst?mom AVG (http://www.grisoft.cz). Verzia: 6.0.394 / V?rusov? datab?za: 224 - d?tum vydania: 3. 10. 2002 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
