in reply to Re^11: DBI Problem
in thread DBI Problem
Where specifically would you suggest I look?
The first query returns the desired result. So the session goes out of scope after that first query is run. Why? And how to work around that? Please show us why you feel $session has a valid value when the first call to executequery gets executed. Please explain why you feel $session goes out of scope after the first query is run. Please explain why you feel a need to flush the session buffers in executequery at all. Please explain what $session has to do with executequery at all.
I am not running anything. My hosting company is running perl. I f you are not running anything how does your website even function. You are running 5.8.8 released 2006-02-02 yet you say that is quite a while for it to go unfixed. Even though the author points out it is not a bug in his code but a fault in YOUR CODE in that you are letting the database get closed before flushing the session data, you complain that it should have been fixed by now even though your perl has not even been updated since before then.
All the other calls to executequery are not followed by a second call. This one is unique. This has nothing to do with executequery except that you wrongly try to flush the session data there. It might help if you hand inspect your code paying attention to when $session gets assigned a valid value, when it is getting used and when it goes out of scope
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^13: DBI Problem
by tultalk (Monk) on Oct 01, 2017 at 00:47 UTC | |
by huck (Prior) on Oct 01, 2017 at 01:39 UTC | |
by tultalk (Monk) on Oct 01, 2017 at 17:19 UTC | |
by tultalk (Monk) on Oct 01, 2017 at 02:28 UTC | |
|
Re^13: DBI Problem
by Anonymous Monk on Sep 30, 2017 at 16:41 UTC |