Re: Re: Re: Multiple date ranges

You don't need to solve this in a non-SQL way.

Take this opportunity to port your database to SQL (build it out of the pipe file).

Then run SQL queries (which is what you're trying to do), so by the time your frontend catches up (the other code), you already have a nice database/search backend all ready.

Using CGI::Application the re-development of your frontend can take lots and lots and lots less time.

Using DBD::SQLite can save you the setup of a real database.

Comment on Re: Re: Re: Multiple date ranges

Replies are listed 'Best First'.
Re: Re: Re: Re: Multiple date ranges by AndyH (Sexton) on Feb 04, 2003 at 08:54 UTC
I looked at CGI::Application and am looking again, as there is an updated version just out, but I am trying to solve the (many) information problems first, before I set about improving the CGI ... I also looked at SQLite, but it's not clear whether it handles Unicode properly or not. The docs don't mention it; the only reference is in the changes file, where it says "fixed Unicode tests". Another problem I have is that some of the data is in XML format and I'm sure you know that mapping XML onto the RDBMS model can be a sure-fire headache generator.	[reply]

Replies are listed 'Best First'.

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

I looked at CGI::Application and am looking again, as there is an updated version just out, but I am trying to solve the (many) information problems first, before I set about improving the CGI ...

I also looked at SQLite, but it's not clear whether it handles Unicode properly or not. The docs don't mention it; the only reference is in the changes file, where it says "fixed Unicode tests".

Another problem I have is that some of the data is in XML format and I'm sure you know that mapping XML onto the RDBMS model can be a sure-fire headache generator.

[reply]