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: Miguel Arroz <email@hidden>
- Date: Thu, 3 Dec 2009 23:10:16 +0000
Hi!
There is nothing "specifically" wrong about using MySQL as a
database for WO. What's wrong is using MySQL at all! ;)
Essentially, it sucks. The first concern of MySQL authors is speed,
and only then correctioness. This may be seen my the existence of
InnoDB itself. First, speeeeeed. A few years later, yeah, this
actually might be usable in something else than a blog if we actually
add ACID properties to it!
In my Univ, the IT team who deals with the central systems moved
everything they could from mysql to PostgreSQL. Among other reasons,
once in a while a MySQL table corrupted itself. PostgreSQL is much
more robust.
As always in software engineering, everything is a compromise.
There may be a few situations where MySQL is dramatically faster than
PostgreSQL, and the inverse is also true, it depends on the usage and
the DB architecture. This to say that you should use what better suits
your needs. But what I would not expect is MySQL to... you know...
work! ;)
Yours
Miguel Arroz
On 2009/12/03, at 22:58, Kieran Kelleher wrote:
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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