StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5774124
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
8
CommunityOwnedDate
CreationDate
2011-04-25T00:20:32.947
FavoriteCount
0
LastActivityDate
2016-05-29T20:44:48.437
LastEditDate
2016-05-29T20:44:48.437
LastEditorUserId
4871972
OwnerUserId
267887
ParentId
5773724
PostTypeId
2
Score
175
ViewCount
0
LastEditorDisplayName
text
Body
What you have is a python error -- <code>self</code> is not defined. <code>self</code> is generally what refers to the class instance itself on class methods. Anyways, I agree, it's brand spanking new and not as documented. I think looking at the source is absolutely key at this point. To get comfortable with class based views, I'd start by subclassing <code>django.views.generic.base.View</code>, which implements only a few methods, namely attempting to call a function on the class based on the request method (post, get, head, - look at source). For example, here's the first step to replace view functions with the new view classes: <pre><code>class MyClassBasedView(View): def get(self, request): # behave exactly like old style views # except this is called only on get request return http.HttpResponse("Get") def post(self, request): return http.HttpResponse("Post") (r'^foobar/$', MyClassBasedView.as_view()) </code></pre> Back to your specific question: All <code>TemplateView.as_view()</code> does is render the template - <code>CreateView</code> is a combination of several other classes that handle <code>ModelForms</code> and template rendering (<code>TemplateView</code>). So, for a very basic example, <a href="https://docs.djangoproject.com/en/1.9/ref/class-based-views/generic-editing/#createview" rel="noreferrer">look to the docs</a> for what class <code>mixins</code> are used by <code>CreateView</code>. We see it implements <code>TemplateResponseMixin</code>, <code>ModelFormMixin</code>, and <code>ProcessFormView</code>, each containing a list of methods for those classes. <hr> <h2>The most basic CreateView</h2> At the most basic level, provide <code>CreateView</code>'s <code>ModelFormMixin</code> with the model or custom ModelForm class <a href="https://docs.djangoproject.com/en/1.8/ref/class-based-views/mixins-editing/#modelformmixin" rel="noreferrer">as documented here.</a> Your <code>CreateView</code> class would look something like the following <pre><code>class AuthorCreateView(CreateView): form_class = AuthorForm template_name = 'author_new.html' success_url = 'success' </code></pre> With those 3 core attributes set, call it in your URLs. <pre><code>('^authors/create/$', Author.AuthorCreateView.as_view()), </code></pre> Render the page and you'll see your ModelForm passed to the template as <code>form</code>, handling the form validation step (passing in <code>request.POST</code> / re-render if invalid), as well as calling <code>form.save()</code> and redirecting to the <code>success_url</code>. <hr> <h2>Start overriding the class methods</h2> To customize behavior, start overriding the methods documented for the <code>mixins</code>. Remember that you simply need to return an <code>HttpResponse</code> from one of these methods just like any regular view function. Example overriding <code>form_invalid</code> documented in <code>ModelFormMixin</code>: <pre><code>class AuthorCreateView(CreateView): form_class = AuthorForm template_name = 'author_new.html' success_url = 'success' def form_invalid(self, form): return http.HttpResponse("form is invalid.. this is just an HttpResponse object") </code></pre> <hr> This per-method overriding starts becoming extremely useful as your forms grow more advanced and ultimately lets you build huge forms with a handful of lines of code, overriding only what is necessary. Say you want to pass your form custom parameters such as the <code>request</code> object (very common if you need access to the user in the form): you merely need to override <code>get_form_kwargs</code>. <pre><code>class MyFormView(FormView): def get_form_kwargs(self): # pass "user" keyword argument with the current user to your form kwargs = super(MyFormView, self).get_form_kwargs() kwargs['user'] = self.request.user return kwargs </code></pre> Class based views are a shining example of smart class usage. It gave me a great intro towards building my own mixins for views and python classes in general. It is saving countless hours. Wow this got long. To think it started as a mere URL to the docs comment :) Hope that helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I use CreateView with a ModelForm
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USYuji 'Tomita' Tomita
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I use CreateView with a ModelForm
 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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.