I don't want to get too far OT but I am in a similar situation as Jaime and
was also planning to use MySQL. This is the first time I've seen or heard
any comments like this and wanted to "poll the audience" to see what people
think and if Greg's sentiments are the norm.
For me, MySQL is perhaps the easiest database server to implement and
maintain. It is dead easy to backup a database in 'clear'. Migrate
databases, and do most of the daily maintainence tasks. As a developer,
it is acceptably fast, has all the basic to intermediate functions
expected of a typically database, including support for UTF-8 (solves my
international language issues).
There is ONE thing about MySQL that gets my goat: it's connection pool
is not as reliably available as other servers (even against MS SQL).
Even in low but constant loads, it does not always serve out a database
connection in the first request, so you have to code specially for
failed requests. I've installed multiple permutations of the version 5,
and it is still like this.
MySQL's licence seems to have increased doubly since the year it charges
for commercial installations (post-3.22). It is still way cheaper than
MS SQL, but now Postgre is starting to look real sexy, and IBM's
DB2-lite has also gone free for commercial use.
Personally I prefer MySQL. But the database landscape is changing, and
loyalty does not survive a product that does not flow with the changing
times.
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs