StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4891652
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-02-03T20:57:39.933
FavoriteCount
0
LastActivityDate
2011-02-03T20:57:39.933
LastEditDate
LastEditorUserId
0
OwnerUserId
436376
ParentId
4891275
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It's no good speculating how Google does it; Whatever Google uses, it's backed by a truly massive server cluster, and is probably far more involved than you need. For a smaller app, even an enterprise-level app, there are straightforward methods to accomplish this. For the schema, I would store the appointment as an ordinary date/time, and the reminder either as another date/time (which you can calculate given hours and minutes using the TimeSpan structure), or as the number of Ticks in a TimeSpan. There are advantages and disadvantages to either; using a date/time reminder, you must recalculate that date/time if the appointment changes. But, the reminder time is human-readable when stored in schema. The opposite is true for storing the value as ticks; 15 minutes in TimeSpan ticks is 15 minutes, and you can add that to any datetime they specify for the actual appointment. But, it's just going to be a big number in the DB, requiring users to use your app to understand the data. You can store one reminder for an appointment on the appointment record itself, or you can allow many pre-scheduled reminders per appointment by maintaining a separate table that references the appointment record and contains the reminder time. For the actual reminder implementation, an app (or piece of functionality therein) that you create to handle these reminders should query the database for the first reminder of interest to the current user that will occur first, and set a timer to expire at the designated time. That thread will simply sleep for the required number of milliseconds, then fire an event which you'll use to show the reminder.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow does Google Calendar do their reminders?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKeithS
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. CO*A* server cluster? :)
 singulars
 PostPostId
 PO
 UserUserId
 USJon Skeet
2. COGood point. MANY server clusters. When a network reaches a certain size it starts becoming irrelevant where they're actually physically located; you need networking hardware you normally see in an ISP's warehouse just to have them all talk to each other.
 singulars
 PostPostId
 PO
 UserUserId
 USKeithS

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.