comment on

While I am sure this problem has been solved since the original post was submitted I figured I would make a suggestion in regard to viewing session.a_session data in MySQL. What is stored in the session.a_session isn't visible by "SELECT a_session FROM sessions WHERE id=?" ... Apache::Session serializes the data before inserting it.

Once your session has been created and your additional session-data has been assigned to your tied hash ($session{foo} = "bar";), dump %session on a SUBSEQUENT VISIT and view the available data. If all works as planned, you will see foo => "bar" along with your session id.

Another (down & dirty) way to verify that session.a_session is indeed receiving the specified data is to "less session.MYD" (MySQL data file) on your web server ... assuming you have access. The output may be hard to understand but you should be able to recognize a session variable here or there.
Just a thought.

author => jeyroz

In reply to Re^2: Apache::Session::MySql using a_session by jeyroz
in thread Apache::Session::MySql using a_session by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks