Richard Dice wrote:
Apart from that, to use Apache::Reload, you need to put a reference to
it in *every* file that you want to have reloaded.
And I've found you have to restart Apache anyway, since it doesn't -- in
my installation at least -- seem to do very much except generate gobs of
error
William McKee wrote:
Let me see if I can line item the specific benefits I get:
I'd agree with all of those, William, but it's only fair to note that
there are downsides:
- There can a considerable performance hit using CDBI over embedded SQL.
- Joins may be done in memory as Perl structures,
Richard Dice wrote:
I've given a presentation on the system
I came up with last summer with a system based on Class::DBI, HTML::Template,
CGI::Application and Apache::SessionX -- it all worked great together.
And I'd like to add that, as the current maintainer of that system, I
wouldn't disagree
If I had parameters withdrawal_amount and margin_available, how would I
define a Data::FormValidator clause to check that
withdrawal_amount=margin_available?
It seems that all the examples assume that the parameters are simple,
and the D::FV documentation on validating complex dependencies
VIPP - wrote:
It appears that I am missing a file.
Any suggestions?
Try another mailing list. This one is for discussion of the
CGI::Application module, not broken code and/or installations.
And I guess my suggestion to RTFM offlist didn't stick.
Stewart
I found that there might be an error in the documentation for
cgiapp_postrun(). The wiki page
http://twiki.med.yale.edu/twiki2/bin/view/CGIapp/OrderOfOperations#Making_the_best_use_of_cgiapp_po,
however, is correct.
Here's a diff that might clear things up:
$ diff Application.pm
This has probably been brought up before, but with no FAQ or archives to
browse, I can't tell.
In testing out CGI::Application, I've got a really simple application
with two run modes:
1. presenting a search form to enter a regex
2. returning the words that match in the /usr/dict/words file,
