Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
- Subject: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]
- From: Kieran Kelleher <email@hidden>
- Date: Thu, 3 Dec 2009 17:58:20 -0500
Miguel, anyone, please enlighten me as to what specifically is wrong
with using MySQL InnoDB as a database for WO because I have not seen
any problem, but then I have not used PostgreSQL or FrontBase either -
so maybe I don't see a problem that I should be concerned about.
-Kieran
On Dec 3, 2009, at 5:41 PM, Miguel Arroz wrote:
Hi!
On 2009/12/03, at 22:32, Kieran Kelleher wrote:
I create new OSCs for most background tasks. The one thing is
that I dispose() on it at the end of the task .... and the
dispose() is only useful if you use ERXJDBCAdaptor is used since
the regular WO 5.3 jdbc adaptor opens two connections for every
OSC and leaves the stupid things open forever. ERXJDBCAdaptor
only opens one db connection and releases it when u call
dispose() IIRC.
Dude! <http://terminalapp.net/webobjects-postgresql-and-db-growing-and-growing/
> ;)
Dude! www.mysql.com - innodb (or cluster NDB) .... doesn't "grow
and grow" (and it is not a "toy", no matter what Chuck says ;-) )
No, it's a disaster! ;)
The "growing" is a side effect of leaving the transaction opening
that happens on PostgreSQL due to its architecture, but the point is
the same, do what I say there to avoid the dumb connection. :)
Yours
Miguel Arroz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden