icalendar devel - Mar 2007 - Recommended db structure for working with icalendar events.

I am relatively new to Ruby and this mailing list.

What are the recommended data structures for storing icalendar events in a
database?  If I want to be able to determine, for example, what events are
valid for a specific date/time, will I need to do this by SQL query or do I
need to create objects of icalendar events stored in the db and then
determine those that are valid?

Should a RRULE property, for example, be stored as one field of a record an
or should the parameters be broken down and stored by FREQ, COUNT, UNTIL and
etc?

Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/icalendar-devel/attachments/20070308/8efa6b78/attachment.html

Das,
As for your RRULE property, currently iCalendar only handles the value
as a single string, so you might as well just store the string.  I''m
currently hacking (slowly, very slowly) on an object model for RRULE.
It''ll take the string and expand it into an composite object, so
storing the string is still going to work.

HTH,
Larry

On 3/8/07, das Dasein <das at dase.in> wrote:
> I am relatively new to Ruby and this mailing list.
>
> What are the recommended data structures for storing icalendar events in a
> database?  If I want to be able to determine, for example, what events are
> valid for a specific date/time, will I need to do this by SQL query or do I
> need to create objects of icalendar events stored in the db and then
> determine those that are valid?
>
> Should a RRULE property, for example, be stored as one field of a record an
> or should the parameters be broken down and stored by FREQ, COUNT, UNTIL
and
> etc?
>
> Tony
>
> _______________________________________________
> icalendar-devel mailing list
> icalendar-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/icalendar-devel
>