In a question concerning databases, Timothy Hospedales asked for
advice about:
>2. What web/software client interface method is best to use and why?
We have had tremendous success with MySQL.
As a database engine for medium size projects (medium size is, oh,
say, anywhere from 10 to 10 million (!) records), I don't think it can be
beat - a powerful, full featured, and more or less Open Source multi-
threading server.
We're using Apache as our web server, with the mod_perl Memory-
Resident Perl implementation. All the code to generate pages is
authored in Perl, with Perl::DBI as the link between Perl and the MySQL
database. Works brilliantly. We also have a fairly significant session
management system written in Java, which also uses talks to the
MySQL database, using the MM MySQL JDBC driver.
>1. Documentation / HOWTOs
[I'm *not* the guy that did all the DB programming on our little project
[I'm the Java guy :)] but I suddenly find myself learning SQL and how to
run and administer MySQL in aide of a "port" of the system we are
doing - so I sympathize with needing to work from the ground up]
Two sources on MySQL:
* the MySQL manual itself (nice 600 page beastie - comes with the
distribution in postscript, html, texi, etc)
* a book published by O'Reilly entitled "MySQL and mSQL" by Yarger,
Reese and King (ISBN 1-56592-434-7). Deals specifically with both
language reference *and* using MySQL in a Perl, JDBC or PHP context.
Andrew
--
Captain Andrew Cowie, rmc BEng
Infantry Officer, Canadian Forces
Director, Shad International
[EMAIL PROTECTED] voice 416-829-3945
