Yeah, the way I do that is have a foreign key with the user in the table with private data and then filter by user when retrieving data in the view.
On Wed, Aug 5, 2009 at 10:11 PM, Maksymus007 <maksymus...@gmail.com> wrote: > > > > > Hi everyone, > > > > I'm sure this has come up in the past, but I sincerely can't find it > > in any of the Django tutorials, documentation, or websites. I > > apologize in advance if I missed something! > > > > I'm trying to develop a website where different users store their own > > sets of contacts / articles / etc. If a user logs in, I only want them > > to have access to their own articles or contacts. As such, I'm > > thinking that storing each individual user's data in their own table > > is the way to go. > > > > However, my question is: how do I actually have Django select the > > proper table? The models and views stay the same, but I need to make > > sure that, given a user name, Django selects the proper table(s). > > > > Is there a tutorial on this? A link? Any advice would be appreciated. > > > > Thanks, > > Wojciech > > and why not to just store user_id column for each table? > Tylko jak to django adminowi powiedzieć... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
