in reply to Re^4: DBI Problem
in thread DBI Problem

Dont you realize that anything after a return statement doesnt get executed? Thats not even just a "perl thing"

I guess you missed "Issue resolved by calling flush() before returning the object."

also note Auto-flushing can be unreliable for the following reasons. Explicit flushing after key session updates is recommended.If the DBI handle goes out of scope before the session variable I tend the read the documentation before i use something written by someone else!

Replies are listed 'Best First'.
Re^6: DBI Problem
by tultalk (Monk) on Sep 30, 2017 at 02:38 UTC

    Yes I read it. Just tried it both ways as shown in code and corrected in text.

    Wit the flush before return, the fact that $session->flush() throws an error:

    Software error:

    Can't call method "flush" without a package or object reference at /home/jalamior/www/httpsdocs/cgi-bin/lib/perl/manageusers.pm line 198. localizes the problem to the executequery.

[reply]

      Ever think of looking at what is in session when you call ExecuteQuery?

      see Re^8: DBI Problem, the problem is not in ExecuteQuery, the problem is where you try to do the $session->flush(); there is nothing to insure session has a valid value in ExecuteQuery.

[reply]
[d/l]

In Section Seekers of Perl Wisdom