Re: Database choices
Re: Database choices
- Subject: Re: Database choices
- From: "Cheong Hee (Datasonic)" <email@hidden>
- Date: Tue, 30 Oct 2007 11:50:27 +0800
I am not a heavy user of database, so my 2 cents here could possibly useful
to those light-weight users of DB in FrontBase and MySQL. Typically, only
my 5% or less time is spent on DB once it is set up. These are not about
the detailed features e.g. performance etc but more from a user's experience
perspective.
Being the users of FrontBase for quite some time, I deployed a few FB
Starter licenses on site and they are stable. Those are FB v3.x. And FB
Enterprise cost at that time was nearly USD40k(to-check). However, the FB
Enterprise is FOC now. So it is good to install, try and deploy it.
Installation is even much easier now than 3.x. Note that the java sdk has
to be 1.5 and above for FB v4.x.
MYSQL v4.x seemed did not fix well in Windows due to some JDBC connector
problem. Until ver 5.x, this issue was resolved. So for those who would
like to try, I suggest MYSQL v5.x is a good way to go. That goes to its
tools too.
Personally, agreed that configuration with MYSQL, is easy via my.cnf. As a
simple user of MYSQL like myself, configuration to bring it up and
replication are reasonably easy. The documentation is fairly complete and
resourceful to the deployment. More importantly, it provides a good chance
to edit the table structure and dump them back when there is a change in
EOModel. That saves a lot of time for DB migration.
Some may not aware that MYSQL is not free! The pricing for InnoDB and MyISAM
are different, being InnoDB is slightly more expensive. FrontBase, AFAIK,
is still FOC for all licenses including Enterprise version.
Cheers
Cheong Hee
------------------------------
Message: 4
Date: Mon, 29 Oct 2007 15:27:29 -0400
From: Kieran Kelleher <email@hidden>
Subject: Re: Database choices
To: Mike Schrag <email@hidden>
Cc: WebObjects Dev <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
WRT MySQL, configuring the /etc/my.cnf file for good InnoDB
performance is trivial enough. The my.cnf is simply a way of putting
all command line launch options in a file.... actually the format is
identical to our beloved WebObjects Properties file. The options are
very well documented in the online manual and in the three sample
config files provided.
About 10 settings and you are done .... they provide three sample
config files. Just pick one as a starting point and go to the innodb
section and configure the properties which are documented there with
comments.
Replication is very easy to setup and works very very reliably since
4.1.XX latest.
I use 4.1.XX latest with 5.0.XX latest "Connector/J" driver. Have not
had chance to move production to 5.0.XX yet since no compelling
reason for standard WebObjects usage.
_______________________________________________
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