OK, I've written and unit-tested the database components - see https://drive.google.com/file/d/0B-thboqjuKZTSjRHTXhqMlo3RlU/view?usp=sharing. Now I could use a little advice on the Django part.
I believe that all that is needed is to have the app call the DB function set_session_user() while logging in the user, passing it the user id. I guess my questions are: 1. Where to put this call? - i.e. in what Django module and function? 2. How to make the call? - Is it just executing a SQL statement like "SELECT set_session_user(<userid>)", or is there a better way? ~ Tx again, Ken On Friday, October 17, 2014 5:46:05 PM UTC-6, Ken Winter wrote: > > Thanks again Carl (and others) ~ > > I agree wıth you that the "DB users" approach seems the most promısıng. > It's the one I will pursue, and certainly glad to share the code when I > have some worth sharing - and quite likely I'll have some more questions > before that, as I try to implement this idea. > > As it happens, I'm leaving on a trip tomorrow, so it may be a while for my > next communiqué on this matter. But I'll be back! > > ~ Ken > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9a61f435-5e94-4f64-99d9-9b7cb44891d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
