Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: Perl books I'd like to have.

by stvn (Monsignor)
on May 17, 2005 at 17:33 UTC ( #457909=note: print w/replies, xml ) Need Help??


in reply to Perl books I'd like to have.

Couple of points about your list.

Perl Object-Relational mapping: Class:DBI

Class::DBI could probably fill the entire book, but that would do a disservice to the other great O/R frameworks out there. Not to mentions the fact that the subject of O/R mapping is a wide and varied topic which is as much theory as it is implementation.

That said, a Class::DBI book would be nice :)

Perl web application frameworks: CGI::Applicaiton, Maypole, CGI::Prototype, etc.

Don't forget about Catalyst, I have not tried it myself, but I have heard nothing but good things about it. I also think that this subject would not fit easily into one book, and separate books per-framework would probably be best.

How to develop, test and maintain large perl projects.

I agree very much on this one. While merlyns book is great, it only covers so much. I would love to see a good book which really delves into large scale design/development/testing/maintainence in any language for that matter.

perl for application testing: WWW::Mechanize, Win32::IE::Mechanize

IIRC chromatic just collaborating on a book on perl testing. I would guess that it has this type of stuff in it.

Anyway, just my 2 cents. Nice list :)
-stvn

Replies are listed 'Best First'.
Why Class::DBI? (was Re^2: Perl books I'd like to have.)
by Jenda (Abbot) on May 19, 2005 at 11:53 UTC

    Now that it was mentioned could anyone tell me some reason why would I want to dumb down my relational database to an object store? I don't know, maybe it feels good to those that only feel comfortable in Perl to be shielded from SQL, but I find this a little silly. Why would I want to use Class::DBI?

    Jenda
    XML sucks. Badly. SOAP on the other hand is the most powerfull vacuum pump ever invented.

      Class::DBI is to a database what DreamWeaver is to HTML.

      You can use it as an object store (or do web page layout), or use it to avoid having to write all that SQL (or HTML) code and just fiddle with the code when the tool doesn't do what you wanted it to.

      It's about productivity.

      You still need to know what you're doing though. A database is a not-very-black box, and web design is only partly about visual design.

      /J

      Why would I want to use Class::DBI?

      I use it for the times when the SQL that I'd be writing is so pointlessly simple and repetitive that it's a better use of my time to get the computer to write it for me. There are enough hooks in Class::DBI for me to write the SQL that I need to write for efficiency reasons so what I gain on the swings I also gain on the roundabouts.

      Do I use it all of the time? Hell no. Sometimes the way I'll be using my data is so far away from the Class::DBI view of the world that I'd spend more time getting around it than using it. For simple CRUD applications however it's a boon.

      IMHO of course :-)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://457909]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (5)
As of 2018-07-21 00:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?















    Results (442 votes). Check out past polls.

    Notices?