Store DateTime::Event::Cron objects ?

[Kaare Rasmussen]

Hi 

I'm using the nice DateTime::Event::Cron module. I do want to save the cron 
schedules in a database. The easiest way would be to stringify and 
destringify the objects. Is this possible?

Re: Store DateTime::Event::Cron objects ?

[Kaare Rasmussen]

I'm using the nice DateTime::Event::Cron module. I do want to save the 
cron schedules in a database. The easiest way would be to stringify and 
destringify the objects. Is this possible?


The same question goes for DateTime::Set objects. Can they be made 
persistent? 

Re: Store DateTime::Event::Cron objects ?

[Matt Sisk]

Hello Kaare,


 I'm using the nice DateTime::Event::Cron module. I do want to save the cron
 schedules in a database. The easiest way would be to stringify and
 destringify the objects. Is this possible?

Since, in essence, DT::E::Cron is designed to convert cron strings into datetime
recurrences, why not use the original cron specification as the string to be
stored?

The original() method will return the string used to construct the object.

Matt

Re: Store DateTime::Event::Cron objects ?

[Kaare Rasmussen]

 Since, in essence, DT::E::Cron is designed to convert cron strings into
 datetime recurrences, why not use the original cron specification as the

The not-so-easy part is my small addition:

The same question goes for DateTime::Set objects. Can they be made 
persistent?

Re: Store DateTime::Event::Cron objects ?

[Matt Sisk]

Quoting Kaare Rasmussen [EMAIL PROTECTED]:
 The same question goes for DateTime::Set objects. Can they be made
 persistent?

Flavio was working on something along these lines, though I'm not sure of the
current status. Check out the following thread:

http://marc.theaimsgroup.com/?l=perl-datetimem=111524990432703w=2

Matt

Re: Store DateTime::Event::Cron objects ?

[Flavio S. Glock]

2005/8/8, Matt Sisk [EMAIL PROTECTED]:
 Quoting Kaare Rasmussen [EMAIL PROTECTED]:
  The same question goes for DateTime::Set objects. Can they be made
  persistent?
 
 Flavio was working on something along these lines

It actually worked, but the performance was too bad for complex sets.
The database was not able to optimize the queries, and the execution
time grew exponentially.

I think the solution for storing in a database still is to iterate the
set and store the dates.

The best alternative would be to use a calendar server.

About making the recurrences persistent - DateTime::Event::ICal can
stringify and instantiate back most recurrences generated with
DateTime::Event::Recurrence and DateTime::Event::ICal.

- Flavio S. Glock