That makes sense. I remember now that I came across a section in the
Docs that talks about extending the User model to store more
information. When using the session it's easy to store things like
queryresults ... . I'll have to figure out how to do that efficiently
when using the User model.
Any
On Jul 2, 12:18 pm, mettwoch wrote:
> Hi,
>
> I write a POS application and several users share the same terminal.
> They use a barcode scanner to point to their badge to login (works
> already). I'd like to keep the session data for every user so that
> when user A leaves the terminal and user
On Jul 2, 9:18 am, mettwoch wrote:
> Hi,
>
> I write a POS application and several users share the same terminal.
> They use a barcode scanner to point to their badge to login (works
> already). I'd like to keep the session data for every user so that
> when user A leaves the terminal and user B
Hi,
I write a POS application and several users share the same terminal.
They use a barcode scanner to point to their badge to login (works
already). I'd like to keep the session data for every user so that
when user A leaves the terminal and user B makes an invoice and user A
comes back to the t
4 matches
Mail list logo
