Those solutions make sense, that was just what I was looking for,
thanks! That should be in the docs somewhere...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send
On Thu, 2007-03-29 at 17:42 -0700, Ben Stahl wrote:
> Hi, I think I understand modeling, and user/session authentication.
> But, what I don't understand is how to use these together to tie some
> object instances (stored in the database) to a specific user. For
> example, I want each
I should be more specific, as you wanted only one instance of a User
to be tied to one instance of a RenderQueue.
And I should at least answer one or two of your other questions.
class RenderQueue(models.model):
user = models.OneToOne(User)
In the view, to create a new RenderQueue instance
class RenderQueue(models.Model):
user = models.ForeignKey(User)
http://www.djangoproject.com/documentation/model-api/#many-to-one-relationships
Hope that helps you along in the right direction!
-Doug
On Mar 29, 8:42 pm, "Ben Stahl" <[EMAIL PROTECTED]> wrote:
> Hi, I think I
Hi, I think I understand modeling, and user/session authentication.
But, what I don't understand is how to use these together to tie some
object instances (stored in the database) to a specific user. For
example, I want each authenticated user of the application to have a
single instance of my
5 matches
Mail list logo
