i've spent some time over the last couple of work days resolving this issue, and it's my hope that fellow monks can help expand my awareness of apache and mod-perl with their responses, although some of this may be distribution-specific (debian woody).
i have an in-house apache server i'm developing for use as a query server, and have just started migrating some working scripts from cgi to mod-perl. the query strategy followed in this specific instance is fairly generic - a frame is displayed in which a user defines parameters that return a set of parent records, from which the user selects a subset for a more detailed summary. as i first started testing under mod-perl, the intermediate stage started returning an erroneous result set, despite the fact that i could execute the sql statement in dbish and retrieve appropriate results.
i won't bore you with the diagnostic steps i took, suffice it to say that it took me a while to spot the apache-perl package in debian (doh). the faulty environment had involved the base apache and libapache-mod-perl packages.
my questions are two and a half-fold
1- why did this work at all, given that i had httpd.conf configured to use mod-perl, but the installed httpd had no perl interpreter? and since it did partially work, why did it fail only in one result set ... i was able to retrieve summaries from the child tables on the selected records, though they weren't the ones i really wanted.
2- during the process, i tried to back away from mod-perl, using debian's apt-get to remove everything and reinstall apache, replacing httpd.conf with the one from the previous working cgi environment. this was not effective - the bad result set continued to be returned in an environment that should have been the same as i had when i started. anyone have any idea why?
i remain, of course, eternally grateful for whatever shards of enlightenment are passed my way.
ralphie
In reply to for mod-perl gurus by ralphie
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |