StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11890010
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-08-09T18:48:05.147
FavoriteCount
0
LastActivityDate
2012-08-09T19:41:11.747
LastEditDate
2012-08-09T19:41:11.747
LastEditorUserId
654031
OwnerUserId
654031
ParentId
11889874
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Override <code>get_queryset</code> and vary on whether one of the fields is posted: <pre><code>def get_queryset(self): if self.request.POST.has_key('competition'): return ScoredEvent.objects.all() else: return super(MyView, self).get_queryset() </code></pre> So, just to explain a little better: you would use your "Tie to Competition" option you mentioned to add a field to the form via Javascript. Then, if the field is sent in the POST, it would switch to using <code>ScoredEvent</code> instead. If you want to automatically switch based on what the object currently is, you'd need to override <code>get_object</code> for that. Something along the lines of: <pre><code>def get_object(self, queryset=None): obj = super(MyView, self).get_object(queryset=queryset) try: return ScoredEvent.objects.get(pk=obj.pk) except ScoredEvent.DoesNotExist: return obj </code></pre> Which basically tries to lookup the object again as if it was a <code>ScoredEvent</code> and returns that version if it finds one, instead of <code>Event</code>. You also might need to similarly override <code>get_form_class</code> to ensure that it validates as a <code>ScoredEvent</code> should if it's a <code>ScoredEvent</code> or is becoming a <code>ScoredEvent</code>: <pre><code>from django.forms import models as model_forms def get_form_class(self): if isinstance(self.object, ScoredEvent): return model_forms.modelform_factory(ScoredEvent, ScoredEventForm) else: return super(MyView, self).get_form_class() </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs there a way to dynamically change the model used in an UpdateView with Django?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USChris Pratt
UserOwnerUserId
1. USChris Pratt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs there a way to dynamically change the model used in an UpdateView with Django?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COSo, if I'm understanding this correctly, the event remains an `Event` unless the admin specifies a competition fk, in which case it becomes a `ScoredEvent`. Is that correct?
 singulars
 PostPostId
 PO
 UserUserId
 USKapura
2. COSee update above.
 singulars
 PostPostId
 PO
 UserUserId
 USChris Pratt

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.