PHP and MySQL
Introducing PHP and MySQL
Some Experiments to start off...
Music Database Examples
PHP, which stands for "PHP: Hypertext Preprocessor", is an open-source HTML-embedded scripting language. This means it is an interpreted programming language that is placed in webpages to effect some action when the webpage is viewed.
Much of its syntax is borrowed from C, Java and Perl with some unique features thrown in. The main goal of the language is to allow web developers to write dynamically generated pages quickly, but you can do much more with PHP.
PHP can do many things that conventional programming languages can do including making connections to databases, requesting data and dynamically constructing webpages based on retrieved/calculated data.
MySQL is one of many web-aware relational database management systems that PHP can talk to - it has many of the ANSI standard SQL commands built in and has many features that allow it to be used by lots og people at the same time - ideal for web-enabled applications.
PHP (a module for Webserver software like Apache) and MySQL (server daemons) live on a web-connected server. Pages calling PHP and/or MySQL commands are also stored on that server with permissions set so that server can execute the pages. The user does NOT see the pages as written by the page author - they see the calculated pages, minus the commands used to get it that way. The webserver notices the file extension (.php or .php3) and parses it looking for embedded commands. If it can execute the commands, it does, if it can't, it winges. The page that results from the calculations is then assembled and sent to the user (the command codes are replaced by results or complaints ). This explains sometimes the delay from page request to receipt of that page as speed of processing is server dependent (and most webservers are doing many things at once already).
Scripts are provided on the pages that link from here (along with links that allow you to execute them live to see their results). Note all querying is live to web - any delays caused in getting answer pages are a function of server traffic at the time you request it, your bandwidth and the grace of any gremlins in the system) - none of which I have any control over, sorry.