Angus Berry wrote:
I appreciate the insight.
I understand that the JDORI plugin has some additional administrative work, but is it production stable?
It is production stable. But it does not scale.
The JDORI has some specific limitations that will become a problem if you run OJB/JDORI against database tables populated with a large number of rows. (large is relative to the java heap memory you can afford).
The reason for this is that the JDORI does not provide an efficient query API for the SToreManager plugin. It does only know Identity based queries ("select * from table where pk=1") and extent queries ("select * from table").
All query filtering is done AFTER the extent (i.e. the whole table) has been loaded into memory!
Please note that this is not an OJB problem, but a limitation of the JDORI plugin API.
Thomas
Is there anyone out there using it in a serious way.
thanks
On Thu, 2004-03-18 at 09:02, Brian McCallister wrote:
The OJB native JDO is both incomplete and undocumented. The backend necessary to support JDO is in place (via the OTM) but I think there just hasn't been enough demand for full JDO support, yet.
It is my personal goal to get a solid implementation into 1.1, but for 1.0 the JDORI plugin is the only real JDO option. It works pretty well from what I hear, but I have only fiddled with it and not built any large apps with it. The biggest thing to do if you want to lessen the need for changes when native JDO is available in OJB is probably to use the OTM directly.
You can also always help implement the JDO API on top of OJB ;-)
-Brian
On Mar 18, 2004, at 8:37 AM, Angus Berry wrote:
I wonder if some could give me a little more in depth status of JDO in RC5.
Specifically, from looking at the mail archives I understand that in addition to the JDO ref. mask, there is some native JDO already implemented. So I'm wondering if what's available is buggy or just incomplete and is this documented anywhere other than looking through the source.
My reason being is I have a facade pattern to OJB as my ORM, but I was hoping to use as much JDO as possible to lessen the change when it becomes fully available.
thanks
--------------------------------------------------------------------- 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]
