Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
- Subject: Re: MySQL [was: Re: Dr. Miguel 'Optimistic Locking' Arroz [was Re: WebObjects stress Testing tool?]]
- From: Chuck Hill <email@hidden>
- Date: Fri, 4 Dec 2009 17:35:39 -0800
On Dec 4, 2009, at 5:27 PM, Guido Neitzer wrote:
On 4. Dec. 2009, at 16:48 , Ramsey Lee Gurley wrote:
[Free]
So is PG, FrontBase, and others so no a major Pro
MySQL Administrator is pretty nice to have. At least I don't have
to shell out $150 on Navicat. Does postgres/frontbase/other have
decent free tools?
PGAdmin always did what I needed when I was on the GUI. Not as nice
as Navicat, but working. But as I do 99% of my DB stuff on the
commandline, I quite like psql. Definitely more than sql92 from
FrontBase with it's weird display and somehow weird syntax for
everything other than SQL.
FrontBaseManager: okay. It's there. It kind of works for most things
I needed.
It has always done what I needed it to... which is not all that much.
Anyway, I've found this discussion very enlightening.
I think it is the first one where actual points were made apart form
"but I like it better".
. and the money thing. Of the other two, I'm probably going to
lean toward Postgres, but I'm wondering... What will I do for admin
tools? I'm not good at remembering cryptic command line options.
PGAdmin.
http://www.pgadmin.org/
Clearly, more study is needed (^_^) Oh, as for the Vertical
inheritance... I was just testing/studying inheritance. I've read
enough about what a waste of time VI is on this list. I know
better than to actually want to use it myself. I've already seen
it fail in MySQL and OpenBase, so I was more interested in why it
was failing than actually attempting to use it.
You might also want to do some perf testing for your needs.
FrontBase can be a very nice option if you are not running in the
situations where it's query optimizer is just not up to the task.
Or, more accurately, makes perverse optimization choices. Version 4.9
has fixed the ones that I kept hitting, but it does still make odd
decisions sometimes.
Also with FrontBase you need to make sure to filter data
appropriately, even when importing or using other tools than EOF -
otherwise, garbage in, server down. I had that a couple times.
Yes!
Nevertheless, FrontBase is easy to install, easy to use with WO, is
SQL92 compliant, has some nice features like the LookSee full text
index, multi-master replication and so on.
And it can be very fast for large datasets, odd query optimization non-
withstanding.
PostgreSQL is a bit more cumbersome to set up, but not really hard
or so, is definitely more robust, has a very good query optimizer
and an "explain analyze ..." that actually works and that gives
useful information. I never found FrontBase particularly helpful in
that department.
I've been using FB for at least 10 years now and I can confidently
state that I have NO idea what the FB query plan information means. I
can tell when it has given up optimization hope and is using brute
force, but that is about it.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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