DBD::SQLite 0.11 is now on CPAN. This upgrades to SQLite 2.4.0, adding views and a few other niceties. I also had to fix the transaction model because running under mod_perl with Apache::DBI it continuously locked up solid. This was because under AutoCommit=0, I would immediately do a "BEGIN TRAN", which locked the database, and even when I issued a commit, it would do "COMMIT TRAN" followed by another "BEGIN" immediately. So now it only does "BEGIN TRAN" when you actually execte some SQL, and just flags whether I'm in a transaction or not. I believe this is how DBD::Sybase does it too.
I also found a couple of bugs in the core SQLite library, which I mailed the author about and he said he'd fix them in the next release (they're nothing major - just cause compiler warnings).
This has me wondering... (Score:1)
I also wonder if there are any free vector/text based solutions out there (besides csv/dbm).
Thanks for the info. I *do* take interest in these posts, in case our Oracle server is taken from us. :(
Re:This has me wondering... (Score:2)
Why don't you find out for me?
Re:This has me wondering... (Score:1)
If I get a chance, I'll give it a shot in the next couple of weeks.
Oh, and in case anyone wants a rough comparison of an RDMS versus a commercial text-based solution (in our case, it was BRS by Dataware Technologies), we had eight databases joined, at roughly 4 GB per database, and I could get about 100,000 results in less than a second. With Oracle, I hit my IO limits on a single unindexed 1GB table before I get results.
And you only think I'm e
PPM? (Score:2)
Re:PPM? (Score:2)
Re:PPM? (Score:2)
Re:PPM? (Score:2)
Re:PPM? (Score:2)