Re: Object Matching, speed issue

Use DBD::SQLite - you are replicating the functionality of a database, so use one. *shrugs*

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

Comment on Re: Object Matching, speed issue

Replies are listed 'Best First'.
Re^2: Object Matching, speed issue by roju (Friar) on Aug 25, 2004 at 19:47 UTC
I finally bit the bullet and started using SQLite on a project of mine, and it's awesome. I couldn't recommend it more.	[reply]
Re^3: Object Matching, speed issue by PerlingTheUK (Hermit) on Aug 25, 2004 at 21:17 UTC
I considered using it, and do so for some parts of my code. this data bit I described actually changes a lot, and a user might have about 50 to 500 different files where the data is stored. Within the files there are different tables and a lot of the calculations I do get very complicated once i have to restore it from the database. Therefore I have not gone this step now. But might. Yet this speed issue is more pressing than my intention to port the whole thing to SQLite. Thanks for the advice. Cheers, PerlingTheUK	[reply]