Sorry to keep asking CGI::Class questions on this
CGI::Application mailing list, but you guys know a lot about
it.
I am convinced that I should give it a try. I have it
installed on my web hosting server, but for practice, it is
easier to have it on my home PC.
I am having trouble
I used to be of that same mindset, and just for grins decided to develop
an entire app using Class::DBI, regardless if I quickly ended up hating
it or not.
And frankly, I love it!
Why? Convenience and ease-of-use. It's much easier (and more
enjoyable!) for me to write a few lines of code to
How is the error handling? I'm writing a CGI::App now with DBI and I
find that most of my time is writing error handling routines. If this
query fails rollback and display an error, otherwise continue, etc. etc.
It is alot of work.
On Fri, 2005-03-04 at 08:36 -0600, Jason A. Crome wrote:
I
On Fri, 4 Mar 2005, David Newman wrote:
How is the error handling? I'm writing a CGI::App now with DBI and I
find that most of my time is writing error handling routines. If this
query fails rollback and display an error, otherwise continue, etc. etc.
It is alot of work.
It seems odd that the
Christopher Hicks wrote:
On Fri, 4 Mar 2005, David Newman wrote:
How is the error handling? I'm writing a CGI::App now with DBI and I
find that most of my time is writing error handling routines. If this
query fails rollback and display an error, otherwise continue, etc.
etc. It is alot of
I am a dummy. I did not mean CGI::Class or CGI::DBI or
whatever I put in that e-mail. sorry!
Mark
-
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http://marc.theaimsgroup.com/?l=cgiappr=1w=2
Hello Jason,
* Jason A. Crome [EMAIL PROTECTED] [2005-03-04 15:34]:
Why? Convenience and ease-of-use. It's much easier (and more
enjoyable!) for me to write a few lines of code to create a class based
upon a table in my database than it is to write a piece of SQL that
updates the same
