On 13/06/2009 1:08 AM, Allen Fowler wrote:
>> What are you doing about timezones and DST? Are "start" and "end" UTC?
>
> For v1, all local times. UTC is not a requirement yet, but if can be added
> with out hassle, then why not.
>
>> Is a location (and by extension a timezone) associated wi
On 12 Jun 2009, at 4:08pm, Allen Fowler wrote:
> If you have any suggestions for how start planning for multiple TZ
> and UTC / DST support, I would be very interested to hear.
All date data should be stored as UTC. It is extremely difficult to
get this right later if you don't start off do
> What are you doing about timezones and DST? Are "start" and "end" UTC?
>
For v1, all local times. UTC is not a requirement yet, but if can be added
with out hassle, then why not.
> Is a location (and by extension a timezone) associated with events like
> face-to-face meetings?
>
No
On 12/06/2009 7:48 PM, Allen Fowler wrote:
> idname kind start
> end length
>
> --
> 3
>
> One table of the events with fields you need (eg description, start and
> end, repeating rule). A second table with the exceptions, or depending
> on how much you want to normalize a table per exception type.
>
> > Where is this calculation being done? In SQL? At the app level? How?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>> 1) How should I be structuring the DB so to store this data sanely.
>> The above is the easiest way if you want to do imports and exports.
>>
>
> I'm not sure what you mean
Unless your system is going to operate in total isolation from the
> > I'm looking for suggestions on how to store and retrieve events for a
> > calendering system in SQlite.
> >
> > For each user there must be:
> >
> > 1) All day events on a specific day.
> > 2) All day events that are repeated over a given date range.
> > 3) All day events that are repeat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Allen Fowler wrote:
> I'm looking for suggestions on how to store and retrieve events for a
> calendering system in SQlite.
The general way this is done, and especially if you want to be
compatible with standards such as vcal/ical is to store events
Hello,
I'm looking for suggestions on how to store and retrieve events for a
calendering system in SQlite.
For each user there must be:
1) All day events on a specific day.
2) All day events that are repeated over a given date range.
3) All day events that are repeat each day from until cance
9 matches
Mail list logo