in reply to Re: Re: Re: Session Problems
in thread Session Problems

Yes, there's some code I didn't post (sorry):

the login code takes a username and password from a form, looks up the username in the DB, and checks to see if the password matches. If it does, it sets $session{userid} to the users userid.

The logout code simply sets $session{userid} to undef.

I may have discovered the problem. As I understand it, there should be a row in the sessions table for each cookie issued, right? I have *no* rows in my sessions table.

I can't shake the feeling that I've completely missed something in how the sessions code works.

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Session Problems
by perrin (Chancellor) on Aug 15, 2001 at 20:43 UTC
    You are correct, there should be one row in the table for each cookie issued.

    I see one thing that may be causing problems. You are trapping errors from the attempted tie to Apache::Session::DBI, but only handling the error if it's from the user not having a saved session. It could be an error from the database, and it's being ignored. Put in an else on that $@ check to re-throw the exception with a die if it doesn't match the regex.

    You know, this session code from the Mason site has a lot of problems. Are you sure there isn't something newer included in the distribution?

[reply]
      I'll take a look and see, though I don't recall anything. Checking the exception isn't a bad idea.
[reply]

In Section Seekers of Perl Wisdom