StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9080230
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-31T13:21:41.990
FavoriteCount
0
LastActivityDate
2012-01-31T13:21:41.990
LastEditDate
LastEditorUserId
0
OwnerUserId
288502
ParentId
6650499
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
In my specific case, I traced this bug down to declarations of ModelAdmin inline in my models.py code causing my model classes to be instantiated incorrectly, with broken <code>on_delete</code> behaviour the most visible side-effect of this. From my commit message: <blockquote> Fixed issue with cascading deletes not being done properly in Django DB. Turns out it's really important to not declare your ModelAdmins at the global scope in models.py, otherwise all the relationships between the different models get calculated before all the models are loaded and lots of them get left out. Really isn't that emphatic about this in the Django documentation. </blockquote> So in my original (broken) code, I would have the ModelAdmin for each Model declared immediately after it, a la: <pre><code>class AccessPeriod( models.Model ): .... class AccessPeriodAdmin( models.ModelAdmin ): .... # This causes the metaclass setup for AccessPeriod to happen right now, # and since related models for AccessPeriod are not all declared yet, # relationship handling behaviour becomes broken for AccessPeriod admin.site.register( AccessPeriod, AccessPeriodAdmin ) class Payment( models.Model ): .... class PaymentAdmin( models.ModelAdmin ): .... # Same effect on the Payment model here admin.site.register( Payment, PaymentAdmin ) </code></pre> The solution was to move all the ModelAdmin declarations out of <code>myapp/models.py</code> and into <code>myapp/admin.py</code> so that all the metaclass setup for each class happens after all the model declarations have been handled, and then all the relationships started behaving properly again.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs Django supposed to implement DB on_delete rules itself?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USglenc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs Django supposed to implement DB on_delete rules itself?
 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
 VTUpMod
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
 VTBountyClose
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.