On Mon, 13 Jun 2005, Dale wrote: > However, the server this currently sits on doesn't and won't ever (not > through choice) have any form of SQL so I'll just have to struggle > with the files. :)
You miss the point of SQLite then. With SQLite -- or the Perl interface, DBD::SQLite -- you're just making SQL-syntax queries to a regular file on disc. There's no server to set up, no software to configure, just a library file that the Perl module will sort out accessing for you. By contrast, if your data is in a CSV format (comma separated values, tab separated values, etc), you could use DBD::CSV to write Perl code that issues SQL queries to the plain-old CSV files, so you could SELECT rows, INSERT values, UPDATE rows, etc. In the background, it's still just a plain text file, but you've not got a better way to work on it. SQLite does more or less the same thing, but the data files it saves are a bit more efficient to work with than CSV. That's about it though. Really, this approach is worth considering. It's very easy to set up, it's very easy to maintain, there's almost no overhead, and if you ever want to upgrade to something better in the future, you won't have to rewrite all your code to make it work. At least give it a look. I think it'll make your life easier, really :-) -- Chris Devers -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
