On 14/11/2013 23:03, Niphlod wrote:
If strictly needed, I'd go with a fixed table ... something like
user_id ref_id
1 2
1 10
1 16
Thanks Nipnlod.
I am already using this technique in another part in the app. Maybe I
must rethink it for the present situation. It will not solve the
problem of one logged in user using more than one session from different
browsers but it can at least solve the problem of one user overwriting
another's data.
I agree, it will be very difficult to manage the temporary tables in the
app. That is why I posted the question. I was hoping that some genius
on this list thought of something I did not think of to solve the problem :)
In this situation using Postgresql's temptables is not possible because
of the database session which is not controlled by which user is using
it, but by the connnection to the database.
Regards
Johann
--
J.H. Spies - Tel. 021-982 2694 / 082 782 0336 / 021-808 4699(w)
Posbus 4668, Tygervallei 7536
"Submit yourselves therefore to God. Resist the devil,
and he will flee from you." James 4:7
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
