Any database using
SQL would fit the description.
SQL allows you to define, create and delete your tables; it is ideally suited to search the database, insert, update and delete records and most databases servers (such as MySQL) are relatively fast.
The DBI-framework and the DBD-drivers allow easy interfacing with most database engines/servers and if you later want to change the underlying database, you can do so with little or no change to your programs (unless you have relied on database specific things -- which you should avoid if you can).
CountZero
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
|
•Re: Re: Database File Advice
by merlyn (Sage) on Jan 13, 2004 at 20:55 UTC
|
Please stop suggesting MySQL for new starts. Read the MySQL gotchas about the failures.
If you want very fast and simple, use DBD::SQLite.
If you want fast and full-featured, use PostgreSQL. MySQL just doesn't cut it any more. "MySQL is sooooo 90's".
| [reply] |
|
|
You know, that same site has PostgreSQL gotchas too.
If someone said "Perl is soooo 90s, use Python instead", you'd likely object. Rightfully so — I would too.
There are good reasons to use either database (and I've used both on different projects), but "it's soooo 90's" is not one of them. People who ask "which database should I use?" deserve better answers.
| [reply] |
|
|
In fairness to both of you, while chromatic is correct, and there is a PostgreSQL gotchas, it only has two entries, while the MySQL gotchas is a lot longer.
MySQL is highly optimised for data retrieval, and is often the best choice for write-once read-many databases. This is what I ususally have, so I use it a lot. It is not necessarily the best choice for other situations. However, if you know it well, it is quite well-behaved.
PostgreSQL is closer to something like Oracle in functionality, but that assumes that Oracle is what you want. Sometimes you do, but quite often you don't.
There's a nice discussion from Philo Vivero
has an interesting (and similar) perspective.
| [reply] |
|
|
| [reply] |