StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8750578
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-05T22:10:56.017
FavoriteCount
0
LastActivityDate
2012-01-05T22:10:56.017
LastEditDate
LastEditorUserId
0
OwnerUserId
236499
ParentId
5848252
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This happens because the fields ordering is defined by UnboundField.creation_counter class, which uses the order the Field class appears in the code. <pre><code>>>> x1 = UserForm() >>> x2 = UpdateUserForm() >>> [(f[0], f[1].creation_counter) for f in x1._unbound_fields] [('first_name', 22), ('last_name', 23), ('middle_name', 24), ('username', 25), ('password', 26), ('email', 27)] >>> [(f[0], f[1].creation_counter) for f in x2._unbound_fields] [('first_name', 22), ('last_name', 23), ('middle_name', 24), ('username', 25), ('email', 27), ('password', 28)] >>> </code></pre> As this is hard to solve (because wtforms try to be magic using this approach), the best way to deal with this is to define the fields in the desired order. <pre><code>class BaseForm(Form): first_name = TextField(u'First name', [validators.Required()]) last_name = TextField(u'Last name', [validators.Required()]) middle_name = TextField(u'Middle name', [validators.Required()]) username = TextField(u'Username', [validators.Required()]) class UserForm(BaseForm): password = TextField(u'Password', [validators.Required()], widget=PasswordInput()) email = TextField(u'Email', [validators.Optional(), validators.Email()]) class UpdateUserForm(BaseForm): password = TextField(u'Password', [validators.Optional()], widget=PasswordInput()) email = TextField(u'Email', [validators.Optional(), validators.Email()]) </code></pre> But if you are perfectionist or need to adhere to the <a href="http://en.wikipedia.org/wiki/Don%27t_repeat_yourself" rel="nofollow">DRY principle</a>: <pre><code>class BaseForm(Form): first_name = TextField(u'First name', [validators.Required()]) last_name = TextField(u'Last name', [validators.Required()]) middle_name = TextField(u'Middle name', [validators.Required()]) username = TextField(u'Username', [validators.Required()]) class UserForm(BaseForm): password = TextField(u'Password', [validators.Required()], widget=PasswordInput()) class UpdateUserForm(BaseForm): password = TextField(u'Password', [validators.Optional()], widget=PasswordInput()) BaseForm.email = TextField(u'Email', [validators.Optional(), validators.Email()]) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POwtforms Form class subclassing and field ordering
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCarlo Pires
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.