StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2978310
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-06-04T23:00:34.180
FavoriteCount
0
LastActivityDate
2010-06-04T23:42:53.737
LastEditDate
2010-06-04T23:42:53.737
LastEditorUserId
192812
OwnerUserId
192812
ParentId
2971198
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It sounds like you want to store a date interval. In Python this would (to my still-somewhat-noob understanding) most readily be implemented by storing two datetime.datetime objects, one specifying the start of the date range and the other specifying the end. In a manner similar to that used to specify list slices, the endpoint would not itself be included in the date range. For example, this code would implement a date range as a named tuple: <pre><code>>>> from datetime import datetime >>> from collections import namedtuple >>> DateRange = namedtuple('DateRange', 'start end') >>> the_year_2010 = DateRange(datetime(2010, 1, 1), datetime(2011, 1, 1)) >>> the_year_2010.start <= datetime(2010, 4, 20) < the_year_2010.end True >>> the_year_2010.start <= datetime(2009, 12, 31) < the_year_2010.end False >>> the_year_2010.start <= datetime(2011, 1, 1) < the_year_2010.end False </code></pre> Or even add some magic: <pre><code>>>> DateRange.__contains__ = lambda self, x: self.start <= x < self.end >>> datetime(2010, 4, 20) in the_year_2010 True >>> datetime(2011, 4, 20) in the_year_2010 False </code></pre> This is such a useful concept that I'm pretty sure that somebody has already made an implementation available. For example, a quick glance suggests that the <code>relativedate</code> class from the <a href="http://pypi.python.org/pypi/python-dateutil/1.5" rel="nofollow noreferrer">dateutil</a> package will do this, and more expressively, by allowing a 'years' keyword argument to be passed to the constructor. However, mapping such an object into database fields is somewhat more complicated, so you might be better off implementing it simply by just pulling both fields separately and then combining them. I guess this depends on the DB framework; I'm not very familiar with that aspect of Python yet. In any case, I think the key is to think of a "partial date" as a range rather than as a simple value. <h3>edit</h3> It's tempting, but I think inappropriate, to add more magic methods that will handle uses of the <code>></code> and <code><</code> operators. There's a bit of ambiguity there: does a date that's "greater than" a given range occur after the range's end, or after its beginning? It initially seems appropriate to use <code><=</code> to indicate that the date on the right-hand side of the equation is after the start of the range, and <code><</code> to indicate that it's after the end. However, this implies equality between the range and a date within the range, which is incorrect, since it implies that the month of May, 2010 is equal to the year 2010, because May the 4th, 2010 equates to the both of them. IE you would end up with falsisms like <code>2010-04-20 == 2010 == 2010-05-04</code> being true. So probably it would be better to implement a method like <code>isafterstart</code> to explicitly check if a date is after the beginning of the range. But again, somebody's probably already done it, so it's probably worth a look on <a href="http://pypi.python.org" rel="nofollow noreferrer">pypi</a> to see what's considered production-ready. This is indicated by the presence of "Development Status :: 5 - Production/Stable" in the "Categories" section of a given module's pypi page. Note that not all modules have been given a development status. Or you could just keep it simple, and using the basic namedtuple implementation, explicitly check <pre><code>>>> datetime(2012, 12, 21) >= the_year_2010.start True </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to deal with "partial" dates (2010-00-00) from MySQL in Django?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USintuited
UserOwnerUserId
1. USintuited
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. COI definitely not storing time intervals. This PartialDate will be use to store mostly birthday dates for peoples, dead and alive. So, frequently, especially for dead peoples, my client do not have the complete date. But it help me in my development to "think of a "partial date" as a range".
 singulars
 PostPostId
 PO
 UserUserId
 USEtienne

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.