Why is it that the globally scoped session would not be visible in the executequery?
Being visible and containing a valid value are two different things entirely
by setting the scope of $session via my when it is assigned you insure it is only visible when it contains a valid value. If you had so limited the scope of session in the beginning then when the desctructor for session tried to run the flush the database would not have been already closed either.
i did not suggest anything with tsid or sid, the logical scoping operator "my" has nothing to do with either of them
In reply to Re^10: DBI Problem
by huck
in thread DBI Problem
by tultalk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |