So is the destroy undefined the problem to chase?
No
you havent been paying attention at all have you? Somehow you still think this has to do with ExecuteQuery but it does not.
You want to make sure the session data is flushed before the database(handle) gets closed.
according to http://search.cpan.org/~markstos/CGI-Session-4.48/lib/CGI/Session.pm#A_Warning_about_Auto-flushing the best way is to use $session->flush(); since Explicit flushing after key session updates is recommended.
Another way would be to use my to lexically localize $session only to the blocks it is being actively used rather than having a lexical-global scope. but that relies on autoflushing by the destructor
In reply to Re^14: DBI Problem
by huck
in thread DBI Problem
by tultalk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |