On Tuesday 04 June 2002 19:59, Jason Teagle wrote: > to be fair, it is customary to get all the tools and other preparations > (including necessary files) ready before embarking on a project. Thus, it > is logical to get a blank database ready before beginning. Why read yards > of documentation before you even have something to practice on as you go? I > didn't try reading the PHP manual before I was able to run PHP scripts > somewhere, so I don't try reading the MySQL manual before having a database > to work on.
If you can get by without reading manuals then good luck to you. > Also, if a person doesn't _know_ that PHP can create a database for you, > how would they know that somewhere in the list of PHP functions is the > answer to the problem? It would be foolish to expect someone to read the > _whole_ of the documentation on MySQL or PHP just to see if there is such a > thing, there's just too much of it. I hope it's not foolish to expect someone to be able to /search/ for the relevant information. In this day of electronic information there's no need to flip through page after page looking for what you need. And even a printed book should have a table of contents and an index to make looking up information quick and painless. That is why I said if you can't be bothered to read the manual, at least find a tutorial. There are _plenty_ of tutorials on how to get started with PHP + MySQL. -- Jason Wong -> Gremlins Associates -> www.gremlins.com.hk Open Source Software Systems Integrators * Web Design & Hosting * Internet & Intranet Applications Development * /* Harriet's Dining Observation: In every restaurant, the hardness of the butter pats increases in direct proportion to the softness of the bread. */ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php