OT: SCO Openserver 6 + MySQL

[Fairlight]

In the relative spacial/temporal region of Fri, Aug 31, 2007 at 12:30:20PM
-0400, Walter Vaughan achieved the spontaneous generation of the following:
> <flame mode on> If you want a *real* database, and you are needing
> the functionality of mySQL5, then you *really* should be looking at
> postgreSQL. mySQL is a <toasty_flame mode> toy </mode> that acts like it
> can handle transactions. mySQL is excelent for read only and web page
> services, but I lost the faith after seeing first hand how you cannot
> trust your data in a transanctional environment.  YMMV </flame mode off>

Oh, I've been waiting years for this opportunity to present itself in
reverse...

"Go ahead, Walter...  Don't hold back--tell us how you -really- feel!"

:)

FWIW, I really didn't like Pg's administrative model.  I think My has a
better model in terms of how the UAL's and other rulesets are recursively
part of the system itself.  I absolutely abhored the way Pg's model worked.
I was working with it for a week when I wrote my IPN integration, and Pg
did not endear itself to me, while My was just a pure joy to work with by
comparison.

That said, if it's actually the case that Pg is better with transactions,
well that will speak for itself.  However, which table types were you
using.  There are at least two, if not three, table types--all with
different functionality--in My.  You can get far better functionality in
terms of locking and transactions with INNODB tables, for instance, but last
I checked only the MyISAM tables supported boolean fulltext search fields.
So it's a tradeoff.  If you blew something on MyISAM tables in
transactions, it might be the table type, not necessarily the entire
engine?  I'm not saying that as an absolute truth, but it's what I read
back at that time led me to believe.  I think one could do row locking,
while the other could do only full table locking, as well...that's one
thing that leads me to believe it's the table type, not the whole engine.

Only INNODB supported raw disk spanning at the time, as well.  It looked
the more professional option, while the boolean fulltext search was very
enticing for some functionality in the other table type if you were to
write a web forum, for instance.

It's also an evolving product.  They're making great strides since v3.
Eventually I have no doubt they'll get there.  At least they -are-
evolving.

As you say, YMMV.

mark->
-- 
The latest synth mixdown...
http://media.fairlite.com/Isolation_Voiceless_Cry_Mix.mp3