First question: Perl all the way (well you're on a perl mailing list) But your Perl knowledge will be useful everywhere. I tought I'd vener need perl for other things than my website, and finally ended up to use it (on win2k) to change every occurence of a word in many files, to create index files from other contents, etc etc.
There are tons of tutorials/documentation/help/mailing lists for Perl There are many modules written so you don't have to reinvent the wheel everytime. There is mod_perl for ultimate perl performance:) Second question: As stated, you'll soon need to use several books. MySQL and Perl for the web is a good start, I just read it last week. It shows some good tricks, but there is a little too much imo. Let me explain: They show how useful it can be to use table definition in order to have automated drop down menus and such, but IMO if your site structure is not that complex and generates significant trafic, you'll have a lot of reading for this (ex: You read the 48 states from the table definition instead of the script.. this makes a query each time the drop is needed and it's not likely to change soon) Also, I found there is way too much CGI printing. Well the book is made of CGI, which I don't like and don't use. I like to make my prints with the complete <tags></tags> and control the ident if the result html file, I like to set semi complex css atributes, etc. The book is still great, I read it pretty fast since most of the stuff in it I had already learned it from reading FAQs on the net and reading the dbi-users mailing list. Some little tricks are good to know. For a start at database design is a book called "Database design for mere mortal" A good DB layout is the key to good data tracking. You should take twice the time to create the database because correcting layout errors once on production is pretty long/hard Then in MySQL.. There is the bible MySQL from Paul Dubois' that is good with many examples, but since versions of mySQL changes everytime, you may read the mysql manual at http://www.mysql.com/documentation/index.html Then I'd move to Perl I'd suggest to read "learning perl" from o'reilly then "programming perl" from o'reilly as well. Then I'd move to DBI if needed There is once again a DBI book from alligator descartes clled Perl DBI which is pretty small and fast to read. This once tho you can get a lot of info by yourself on the internet and by looking at examples, because using DBI is not too hard, and Paul Dubois' book that you have covers plenty of DBI. My 2 cents Sorry for the long post Etienne Adam Turoff wrote: > > On Wed, Nov 28, 2001 at 12:38:48PM -0500, [EMAIL PROTECTED] wrote: > > Can anyone tell me why he/she will choice PERL over PHP? > > There are lots of reasons. The most important reason to use Perl > instead of PHP is that Perl is useful in many areas - web programming > as well as system administration and automation of routine tasks. > PHP on the other hand is amost exclusively used with web programming only. > > If you use Perl, there are many more ways you can apply your knowledge. > Not everything is a web app after all. > > > What is the difference between mysql and MySQL (case sensitivity)? > > Just a difference in casing. "MySQL" is the proper casing, but there's > nothing wrong with "mysql". > > > Lastly what is a good book for a developer who is interested in > > implementing > > a WEB-based database using MySQL and PERL? > > > > PS: I have the Paul DuBois book on "MySQL and Perl for the WEB", > > which is very good, but I am looking for a second source of reference. > > Pretty soon you'll need a good book on Perl and another good book on > MySQL / databases. There is no one good MySQL+Perl book out there that > will answer all of your questions or show you all of the concepts you > need to master. > > Z. > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Etienne Marcotte Specifications Management - Quality Control Imperial Tobacco Ltd. - Montreal (Qc) Canada 514.932.6161 x.4001 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
