StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14508663
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-01-24T18:56:02.027
FavoriteCount
0
LastActivityDate
2013-07-31T19:52:57.440
LastEditDate
2017-05-23T11:54:39.930
LastEditorUserId
-1
OwnerUserId
623735
ParentId
4625712
PostTypeId
2
Score
188
ViewCount
0
LastEditorDisplayName
text
Body
If you need to selectively (for just one app) reset migrations that are taking too long, <a href="https://stackoverflow.com/a/12823039/623735">this</a> worked for me. <pre><code>rm <app-dir>/migrations/* python manage.py schemamigration <app-name> --initial python manage.py migrate <app-name> 0001 --fake --delete-ghost-migrations </code></pre> Don't forget to manually restore any <a href="http://south.aeracode.org/wiki/Dependencies" rel="nofollow noreferrer">dependencies</a> on other apps by adding lines like <code>depends_on = (("<other_app_name>", "0001_initial"),("<yet_another_app_name>", "0001_initial"))</code> to your <code><app-dir>/migrations/0001_initial.py</code> file, as the first attribute in your migration class just below <code>class Migration(SchemaMigration):</code>. You can then <code>./manage.py migrate <app-name> --fake --delete-ghost-migrations</code> on other environments, per <a href="https://stackoverflow.com/a/12823039/623735">this SO answer</a>. Of course if you fake the delete or fake the <code>migrate zero</code> you'll need to manually delete any left-over db tables with a migration like <a href="https://stackoverflow.com/a/15799023/623735">this</a>. A more nuclear option is to <code>./manage.py migrate --fake --delete-ghost-migrations</code> on the live deployment server followed by a [my]sqldump. Then pipe that dump into [my]sql on the environments where you need the migrated, fully-populated db. South sacrilege, I know, but worked for me.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the recommended approach to resetting migration history using Django South?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. UShobs
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
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
1. COThis is the best answer, I hope it gets upvoted more.
 singulars
 PostPostId
 PO
 UserUserId
 USchrisv

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.