Hi,
After a very long week of annoying bug with Perl and Apache::Session::MySQL I
was able to solve it (actually Ami Ben Hayon solve it, so thanks
again).
Anyway, every time I updated the content of the session, and arrived to the end
of the script, I made a "disconnect" call to the db handler.
After doing so, I would received an error message from Apache::Session::DBI,
that the connection closed, and it tried to implement some actions
on a close connection.
I made something like that:
$session {'somekey'} = SomeValue;
$session {anotherkey} = $MoreValue;
..
untie (%session);
$dbh->disconnect();
# End of script
Ami found that the Apache session module for some weird reason keep on writing
to the database alto the script already finished to run.
We can't understand why or how.. but that does not matter now.
The solving of the problem was as follow:
$session {'somekey'} = SomeValue;
$session {anotherkey} = $MoreValue;
..
tied (%session)->save;
untie (%session);
$dbh->disconnect();
# End of script
Now we forced the data to be written, and the session does not need to write
the values when the script is stopped it's execution.
I hope this will help other people to solve any similar problems with Apache
Session. And you can feel free to ask me more questions
about it.
Ido
--
Optimization hinders evolution.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
