Wednesday, February 26, 2014

generic.UpdateView and readonly ForeignKeys

I'm looking for a quick and easy way to implement readonly ForeignKeys
when using the generic.UpdateView.

I can't see anything that looks simpler than just ditching the
UpdateView and writing a function based view that sets the FK queryset
to a single object.

Or have I missed something?

cheers
L.

--
From this perspective it is natural that anarchism be marked by
spontaneity, differentiation, and experimentation that it be marked by
an expressed affinity with chaos, if chaos is understood to be what
lies outside or beyond the dominant game or system. Because of the
resistance to definition and categorisation, the anarchist principle
has been variously interpreted as, rather than an articulated
position, "a moral attitude, an emotional climate, or even a mood".
This mood hangs in dramatic tension between utopian hope or dystopian
nihilism...
-----
http://zuihitsu.org/godspeed-you-black-emperor-and-the-politics-of-chaos

--
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+unsubscribe@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/CAGBeqiPwCmwrgo7f9X5NNLh1kDkJ2wrB6EgKvCH_XCQOJFQV6w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment