Moving the implementation is out of my hands.
JDO for RDBMS is an ORM solution which doesn't necessarily answer the question, why not use both (JDBC and ORM)? I think both solutions have merit and I think that many try to make one solution work for both OLAP and OLTP.
/robert
Leon Rosenberg wrote:
And you can't move it to oodbms?
Btw, there are JDO implementation for RDBMS (for example KODO JDO by Versant).
Makes moving easier...
leon
-----Urspr�ngliche Nachricht-----
Von: Robert Taylor [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 13. M�rz 2005 16:19
An: Struts Users Mailing List
Betreff: Re: AW: [OT] ORM vs JDBC vs OODBMS (was [OT] ORM vs JDBC)
An existing production RDBMS implementation :)
/robert
Leon Rosenberg wrote:
Leon,
I have zero experience with OODBMS, so I can't comment on that.
I guess my question was geared more towards RDBMS.
It was an answer :-)
Do you have any real requirements which forces you to use rdbms?
leon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
