Re: Multiple date ranges

I agree that using a SQL model is best. Have you looked at DBD::AnyData? It sounds like you may be able to use it without porting to a database -- just pointing it to your data. I never used it though, so I'm no expert. I started down that path once but ended up importing the data to an existing relational DB instead.

Comment on Re: Multiple date ranges

Replies are listed 'Best First'.
Re: Re: Multiple date ranges by AndyH (Sexton) on Feb 04, 2003 at 08:46 UTC
I did look at AnyData before, as the data on this project is in both pipe-delimited (i.e. CSV) and XML and because it offered both DBD and Perl flavour access, but I didn't have much luck with it - specifically, it wouldn't (for me, anyway) save back changes to the XML (even though I took note of the caveat about having to specifically do adExport). In fact, I had lots of trouble with adExport. And, searching around, I couldn't find any code using it for XML. So, I sort of gave up on it. Maybe it's time to update the XML::Parser and XML::Twig and try again ...	[reply]

Replies are listed 'Best First'.

Re: Re: Multiple date ranges
by AndyH (Sexton) on Feb 04, 2003 at 08:46 UTC

I did look at AnyData before, as the data on this project is in both pipe-delimited (i.e. CSV) and XML and because it offered both DBD and Perl flavour access, but I didn't have much luck with it - specifically, it wouldn't (for me, anyway) save back changes to the XML (even though I took note of the caveat about having to specifically do adExport). In fact, I had lots of trouble with adExport. And, searching around, I couldn't find any code using it for XML. So, I sort of gave up on it.

Maybe it's time to update the XML::Parser and XML::Twig and try again ...

[reply]