On Apr 29, 2005, at 10:51 AM, Dave Rolsky wrote:
Surely implementation of that data type is just a SMOP!
What would the data type look like, exactly? You might be able to
create it using DOMAINS in PostgreSQL.
http://www.postgresql.org/docs/current/static/sql-createdomain.html
Hehe. Actually,
On 4/29/05, Dave Rolsky <[EMAIL PROTECTED]> wrote:
> Has anyone done any work on this?
A little. And I haven't come up with anything more clever then
rollout occurrences when requested, and cache them. If someone does
come up with something, I'd love to hear about that. I've always felt
like th
On Fri, 29 Apr 2005, kellan wrote:
Actually recurrence exceptions are one really good reason why its hard
to ever come up with an elegant, purely rule based recurrence
representation. For events involving humans its inevitable that
sometimes this month's occurrence will get cancelled or re-schedul
On Fri, 29 Apr 2005, Flavio S. Glock wrote:
Dave Rolsky wrote:
Has anyone done any work on this?
Basically, I'd like to be able to store these in a way that makes queries
like "all the entries for a given month" reasonably efficient.
[...]
What I'd really like to see is some way to query both sin
Dave Rolsky wrote:
Has anyone done any work on this?
Basically, I'd like to be able to store these in a way that makes
queries like "all the entries for a given month" reasonably efficient.
[...]
What I'd really like to see is some way to query both single events and
recurring events within a gi
On Fri, 29 Apr 2005, Dave Rolsky wrote:
What I'd really like to see is some way to query both single events and
recurring events within a given timeframe, all in one query that returns a
sorted array of occurrences.
Specifically, I'm interested in offering a meetup.com-alike service
through VegG
On Thu, 28 Apr 2005, David Wheeler wrote:
On Apr 28, 2005, at 10:48 PM, Dave Rolsky wrote:
What I'd really like to see is some way to query both single events and
recurring events within a given timeframe, all in one query that returns a
sorted array of occurrences.
I haven't tried it (yet), but
Dave Rolsky wrote:
- Allow only a fairly limited set of recurrences, store them as iCal
strings, and query based on string contents. This limits the
flexibility of the system, but is potentially quite efficient.
This is what I've done in the past. The iCal string is only the
recurrence part. I
