On Friday 06 May 2005 12:19, Dave Rolsky wrote:
> On Fri, 6 May 2005, Simon Perreault wrote:
> > I don't agree with that. What's wrong with the correctness of data using
> > XML? XML is a way to enforce correctness in data. Sure, a DBMS also
> > enforce correctness in data, but if that's all you ne
On Fri, 6 May 2005, Simon Perreault wrote:
I don't agree with that. What's wrong with the correctness of data using XML?
XML is a way to enforce correctness in data. Sure, a DBMS also enforce
correctness in data, but if that's all you need then you'll probably be
better off using XML. It provides e
Simon Perreault wrote:
That would create N views (not counting the sub-views).
It doesn't create temporary tables anymore:
my $set = DateTime::Event::Recurrence->monthly(
days => [ 10, 20 ], hours => 7 )->
union(
DateTime::Event::Recurrence->monthly(
On Friday 06 May 2005 11:13, Dave Rolsky wrote:
> The purpose of putting something in a DBMS
> is to ensure _correctness_ of the data, and to make it easier to query
> that data in a variety of ways, particularly in ways you did not
> anticipate when you first created the logical model. Speed may
On Thu, 5 May 2005, Simon Perreault wrote:
... ok, now that we got the argument "this is data" out of our way, let's
focus on why one would want to put a particular kind of data in a DBMS or
not. The whole purpose of a DBMS is *quick retrieval*. That's it. Otherwise,
you might just as well use flat
Stephen Gowing wrote:
Hi,
DateTime::Set 0.21 dies when as_list is asked to produce a list from
outside the range of the set. It shows up in the tests included with
DateTime::Event::ICal.
Can't call method "is_infinite" on an undefined value at
/usr/lib/perl5/site_perl/5.8.3/DateTime/Set.pm line
On May 5, 2005 20:03, Dave Rolsky wrote:
> The set _is_ data!
Sure, just as a procedure is data itself. This is data:
sub sum { return shift + shift; }
What's the difference between code and data eh? Is this data?
sub closure {
my $data = shift;
return sub data { return $data; }
