"Keep the browser simple - with a single route in (http) to a server." That's the philosophy behind the web and one of the things that's made it a huge success. It means that a straightforward browser can contact a single server, and Joe Public, Joan Whiting and Mahatma Ali can all view content. But that means that the complexity of storing and accessing data has to be dealt with on the web server, and the straightforwardness of the browser interface is counterbalanced by some quite complex server side systems. It makes sense, really - for every 1000 browsers there might be one server, and it's far better to have one complicated system that a thousand.

Yesterday afternoon, I put together a demonstration showing these various server side elements. A browser, contacting a web server. And then, behind the scenes, the web server running a Perl program via the CGI interface, and that Perl program in turn contacting a MySQL database server for the actual data. And another couple of sample programs (at the proof of concept level) to add more data to the tables. It's rather a long demo so that - rather than post it all here - I've put a full description in our solution centre
here and I've put all the source files
here. You can even try out
the general display page, the
Add Operation Page and the
Add Patient pages ... although (for server security) I've commented out the line that would save your additions to the tables on our live server
I'm not going to risk people entering patients who's names read like adverts!

The demonstration uses the example of medical patients and the operations that have had in two MySQL tables, joined to produce the final results, but the same principles would apply to estate agents selling houses, and to railway trains making station stops!
(written 2008-11-15, updated 2008-11-16)
22b8
Associated topics are indexed under
P308 - Using SQL Databases from Perl [3099] Perl - database access - DBD, DBI and DBIx modules - (2010-12-22)
[2561] The future of MySQL - (2010-01-03)
[2381] Checking the database connection manually - (2009-08-28)
[1904] Ruby, Perl, Linux, MySQL - some training notes - (2008-11-23)
[1224] Object Relation Mapping (ORM) - (2007-06-09)
[975] Answering ALL the delegate's Perl questions - (2006-12-09)
[644] Using a MySQL database from Perl - (2006-03-13)
[515] MySQL - an FAQ - (2005-12-03)
P420 - SQL databases from a browser via Perl and CGIS156 - Interfacing Applications to MySQL Databases [3455] MySQL, MySQLi, PDO or something else - how best to talk to databases from PHP - (2011-09-24)
[3447] Needle in a haystack - finding the web server overload - (2011-09-18)
[3035] How to display information from a database within a web page - (2010-11-07)
[2790] Joining a MySQL table from within a Python program - (2010-06-02)
[2745] Connecting Python to sqlite and MySQL databases - (2010-04-28)
[2263] Mysqldump fails as a cron job - a work around - (2009-06-30)
[1561] Uploading to a MySQL database through PHP - examples and common questions - (2008-03-02)
[1518] Downloading data for use in Excel (from PHP / MySQL) - (2008-01-25)
[1450] Easy selection of multiple SQL conditions from PHP - (2007-11-30)
[1381] Using a MySQL database to control mod_rewrite via PHP - (2007-10-06)
[723] Viewing images held in a MySQL database via PHP - (2006-05-17)
[663] Python to MySQL - (2006-03-31)
[104] mysql_connect or mysql_pconnect in PHP? - (2004-10-30)
Some other Articles
Ruby mixins, modules, require and includeFind the linkRuby Programming Course - Saturday and SundayKeys to friendless churchesHiding a MySQL database behind a web pageRecession? Depression?Spa Road Garage and Convenience Store, MelkshamWiltshire Council says - part 2Wiltshire Council says - part 1Melksham Chamber of Commerce, or the FSB