RJ Herrick am Sonntag, 5. Februar 2006 01.03:
> Thanks to the Johns for their responses, but I believe perhaps I was
> unclear about my intent.
>
> In validating my form input I look at my DB tables to see what types of
> input they will accept (valid values, maxlength, NULL ok, etc). This
> data i
Thanks to the Johns for their responses, but I believe perhaps I was
unclear about my intent.
In validating my form input I look at my DB tables to see what types of
input they will accept (valid values, maxlength, NULL ok, etc). This
data is about the database, not the values coming in off th
now when i run it from the command line i get 2 pages or debug type
info, from the brower i get nothing, error_log also show nothing.
is there a setting in httpd.conf that tells it not to log stuff?!?!?
i think that it is not running the DBI->connect code,
have i got modperl setup right?
have i
Try:
my $dbArgs = { RaiseError => 1, AutoCommit => 0 , TraceLevel => 3 };
my $dbh = DBI->connect( $db, $dbUser, $dbPass , $dbArgs );
while you `tail -f` the errorlog ( /usr/local/apache2/log/error_log
on my system )
the tracelevel will show you exactly what's going on within DBI.
On
that did not help, still no errors, still not good output.
At 06:10 a.m. 5/02/2006, Frank Wiles wrote:
On Sat, 04 Feb 2006 20:45:05 +1300
Derek Robson <[EMAIL PROTECTED]> wrote:
> I am new to the world of modperl.
>
> Any help would be nice.
>
> I have some perl code that runs fine from the c
Jonathan's right, the overhead of caching data shared between apache
processes is probably more than a DB call using a cached DBI handle.
For multi page forms I just keep it all in hidden form fields between
pages, validating as we go, then revalidate all the fields before
finally comitting to
what exactly do you want to cache?
the form inputs or the forms?
if its the forms themselves, you could cache in mod_perl before the
fork, or use somthing like memcached
otherwise , you're best off with a db
you can't use modperl, because caching will be per-child -- you
might put somet
Andrew Ho wrote:
> Hello,
>
> I have a mod_perl (Apache 1.3.33, mod_perl 1.29) handler which returns
> HTTP error codes on several conditions, and uses a custom_response() to
> set a custom body. The custom body is XML (this is a middleware
> component and errors are read by machines, not humans
Hello,
I have a mod_perl (Apache 1.3.33, mod_perl 1.29) handler which returns
HTTP error codes on several conditions, and uses a custom_response() to
set a custom body. The custom body is XML (this is a middleware component
and errors are read by machines, not humans), so I'd like to send a
"
On Sat, 04 Feb 2006 20:45:05 +1300
Derek Robson <[EMAIL PROTECTED]> wrote:
> I am new to the world of modperl.
>
> Any help would be nice.
>
> I have some perl code that runs fine from the command line but not
> with modperl.
>
> #!/usr/local/bin/perl
> use strict;
> use DBI;
> print "Content-
hello,
See here please,
http://perl.apache.org/docs/1.0/guide/debug.html
this doc written by Stas Berkman show us the full debug skills under mod_perl.
Hope that helps.
-Original Message-
>From: Ken Perl <[EMAIL PROTECTED]>
>Sent: Feb 4, 2006 5:37 AM
>To: modperl@perl.apache.org
>Subject
hi,
Debuging a perl program at command line is using -d option, but this
can't be used in a modperl program, any doc or examples on this topic
about how to debug a modperl program?
--
perl -e 'print unpack(u,"62V5N\"FME;G\!E
12 matches
Mail list logo
