StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20156882
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-23T00:21:41.107
FavoriteCount
0
LastActivityDate
2013-11-23T00:21:41.107
LastEditDate
LastEditorUserId
0
OwnerUserId
2125540
ParentId
19330814
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You can implement the <a href="https://pypi.python.org/pypi/python-dateutil" rel="nofollow">python dateutil</a> rrule in postgresql. <pre><code>CREATE OR REPLACE FUNCTION _pc_after( t_rule TEXT, t_after TIMESTAMP, inc BOOLEAN DEFAULT TRUE) RETURNS TIMESTAMP AS $$ from dateutil.rrule import * from dateutil.parser import * rule = rrulestr(t_rule) _after = parse(t_after) occurence = rule.before(_after, inc=False) return occurence $$ LANGUAGE 'plpythonu' VOLATILE; -- = simple before function = CREATE OR REPLACE FUNCTION _pc_before( t_rule TEXT, t_before TIMESTAMP, inc BOOLEAN DEFAULT TRUE) RETURNS TIMESTAMP AS $$ from dateutil.rrule import * from dateutil.parser import * _rule = rrulestr(t_rule) _before = parse(t_before) occurence = _rule.before(_before, inc=False) return occurence $$ LANGUAGE 'plpythonu' VOLATILE; -- = simple between function = CREATE OR REPLACE FUNCTION _pc_between( t_rule TEXT, t_after TIMESTAMP, t_before TIMESTAMP, inc BOOLEAN DEFAULT FALSE) RETURNS SETOF TIMESTAMP AS $$ from dateutil.rrule import * from dateutil.parser import * _rule = rrulestr(t_rule) _after = parse(t_after) _before = parse(t_before) occurences = _rule.between(_after, _before, inc) return occurences $$ LANGUAGE 'plpythonu' VOLATILE; CREATE OR REPLACE FUNCTION _pc_between( t_rule TEXT, t_after TIMESTAMP, t_before TIMESTAMP, inc BOOLEAN DEFAULT FALSE) RETURNS SETOF TIMESTAMP AS $$ from dateutil.rrule import * from dateutil.parser import * _rule = rrulestr(t_rule) _after = parse(t_after) _before = parse(t_before) occurences = _rule.between(_after, _before, inc) return occurences $$ LANGUAGE 'plpythonu' VOLATILE; </code></pre> So : <pre><code>SELECT _pc_between('DTSTART:20130102T090000 RRULE:FREQ=DAILY;INTERVAL=10;COUNT=25', cast('2013-01-01' as timestamp), cast('2013-05-31' as timestamp) ); </code></pre> will return : <pre><code>"2013-01-02 09:00:00" "2013-01-12 09:00:00" "2013-01-22 09:00:00" "2013-02-01 09:00:00" "2013-02-11 09:00:00" "2013-02-21 09:00:00" "2013-03-03 09:00:00" "2013-03-13 09:00:00" "2013-03-23 09:00:00" "2013-04-02 09:00:00" "2013-04-12 09:00:00" "2013-04-22 09:00:00" "2013-05-02 09:00:00" "2013-05-12 09:00:00" "2013-05-22 09:00:00" </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPostgreSQL: Construct a Query That Takes a Date Range
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFrViPofm
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. This table or related slice is empty.
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.