Re: UU code

[sergey@total-knowledge.com]

Got it, I guess I misunderstood recent discussion about DB pooling.

> Session_info should never haver more than one entry. I'm not sure how you
> can use current date in session_info.
>
> 2007/3/16, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>>
>> Yes, I do have a code for this already.
>> Another thing perhaps can be added is 'current date' column, it can be
>> useful in DB pool functionality, I'm not sure though.
>> Do you think we may need entry creation date if session_info may have
>> more
>> than one entry?
>>
>> > We can, but then we have to pass it in the login() as a parameter.
>> >
>> > 2007/3/16, sergey@total-knowledge.com <sergey@total-knowledge.com>:
>> >>
>> >> >> <snip getSessionInfo stuff>
>> >> >>
>> >> > You may want to change all that to key the temp login table
>> >> > off of session ID rather then user ID. This way you don't need to
>> >> > save any extra info in session itself.
>> >> >
>> >>
>> >> Can we have sessionid column in session_info table then?
>> >>
>> >>
>> >>
>> >
>> >
>> > --
>> > Alexey Parshin,
>> > http://www.sptk.net
>> >
>>
>>
>>
>
>
> --
> Alexey Parshin,
> http://www.sptk.net
>