|
Re: Re: DBI modules for database representation in plain files
by davido (Cardinal) on Feb 25, 2004 at 16:44 UTC
|
I second this. I use DBD::SQLite with DBI all the time, and have found it to be an excellent solution in every application I've had for it. Certanly there will be times that more traditional databases are required, but I haven't found that time yet.
From the DBD::SQLite POD:
SQLite is fast, very fast.
It is! It is also happens to be a complete RDBMS database engine wrapped in one convenient module.
| [reply] |
|
|
davido,
It is also happens to be a complete RDBMS database engine
That is a bit misleading since some people would argue that the omitted SQL Features make it incomplete. Since I have very limited db experience, I am not going to make that case. I like SQLite very much and have used it on at least 3 projects now. I also here there may be locking issues with too many concurrent updates. I guess someone deciding what to use knows their own requirements well enough to know if SQLite is right for the job.
Cheers - L~R
| [reply] |
|
|
If it's misleading I didn't intend it to be. The POD for SQLite states, "SQLite is a public domain RDBMS database engine..."
The POD also states that it "Implements a large subset of SQL92", and is "A complete DB in a single disk file..."
So you're right that only a "large subset" is implemented, but I think that's probably the case with many individual SQL implementations.
What I meant by "complete" is that in one package you have just about everything you need. I didn't mean that its SQL implementation supports everything in the SQL92 spec. However, my practical usage has yet to encounter a need for those few edge cases of unsupported SQL features.
| [reply] |
|
|
|
|
|
|
| [reply] |
Re: Re: DBI modules for database representation in plain files
by filipe (Novice) on Feb 25, 2004 at 16:44 UTC
|
Yes.
I've forgot two say that here i would prefer a PURE PERL that is no external code to compile.
so any DB file type that comes bundled with perl distrib. would be great.
Thanks
Filipe
| [reply] |
|
|
Well, by limiting yourself in this way you are basically stuck with either MLDBM (using GDBM or DB_File), or one of the text-based things you mentioned. If you really think performance is going to be a big issue, use MLDBM. If you can't live without SQL support and still need performance, you have to bite the bullet and get a real database.
| [reply] |
|
|
:=)
Guess i'll try to use DBD::Sprite for start.
Iff performace is a issue i'll just have to convince
the guy who will use the script to use DBD::SQLite
The only issue is that he must convince the owner of the web server ... ho well
Thanks anyway
Filipe
| [reply] |
|
|
What is nice about compiling DBD::SQLite is that all the code is contained in the dist. A lot easier than installing mysql, postgresql, ...etc. I have installed on a variety of *nixes without any problems.
I'm sure you are aware of this, just my 2 cents.
sth
| [reply] |