StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20272237
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-28T17:54:37.417
FavoriteCount
0
LastActivityDate
2013-12-03T16:02:37.107
LastEditDate
2013-12-03T16:02:37.107
LastEditorUserId
45698
OwnerUserId
45698
ParentId
19965769
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
My investigations into this are in the question as a set of edits, but the long and short of this is that changes to the to_python method between 1.4 and 1.5 mean that anything that is neither a valid datetime.date nor datetime.datetime must be a string in order to pass through. It looks (without too much further digging) as if the <code>django.utils.encoding.smart_str</code> method was removed in 1.5, and although it's been replaced by <code>smart_text</code>, this never made it into the <code>to_python</code> method. I have raised a ticket in the django Trac instance, <a href="https://code.djangoproject.com/ticket/21523" rel="nofollow">https://code.djangoproject.com/ticket/21523</a> I have also created a patch for this issue - but obviously this may never make it in (and the patch is for 1.5.x, which is already out-of-date, so I really wouldn't count on this making it in). [EDIT 1: a solution!] There is a solution ;-) - I have done a write up here - <a href="http://tech.yunojuno.com/mocking-dates-with-django" rel="nofollow">http://tech.yunojuno.com/mocking-dates-with-django</a> - the key is overriding the FakeDate instancecheck method, so that when comparing a real datetime.date to a FakeDate you get True. I have put together a gist with some sample FakeDate classes and associated tests for reference - <a href="https://gist.github.com/hugorodgerbrown/7750432" rel="nofollow">https://gist.github.com/hugorodgerbrown/7750432</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to mock datetime.date.today() method in Django 1.5.5 tests
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USHugo Rodger-Brown
UserOwnerUserId
1. USHugo Rodger-Brown
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to mock datetime.date.today() method in Django 1.5.5 tests
 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
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.