What database do you use on Debian?
Submitted by sneex on Thu 17 May 2007
| Oracle |
   9% | 129 votes |
| PostgreSQL |
25% | 353 votes |
| MySQL |
62% | 882 votes |
| MaxDB |
0% | 0 votes |
| ISAM |
0% | 2 votes |
| SQL Flat files |
0% | 3 votes |
| Custom In-House |
0% | 2 votes |
| Other |
2% | 39 votes |
| Total 1410 votes |
Recently I've installed PostgreSQL and MySQL to improve my SQL skills. I could have installed IBM's DB/2 and/or Oracle if I could have been bothered to jump through the whoops on their web site.
At work we run some stuff on MySQL (RH/Debian) and at least one Debian box is running SAP/MySQL MaxDB.
Our AIX/Red Hat boxen at work run Informix and if we are allowed to upgrade they'll run DB/2.
--
"It's Not Magic, It's Work"
Adam
[ Parent ]
mysql for the php "goodies" like phpbb ..
Pablo .
[ Parent ]
I use a MySQL because it simple to install and use. And i think it's universal for many purposes.
[ Parent ]
Seriously, I have written commercial Java/J2EE web projects that were deployed on Linux, and they all used Derby successfully.
[ Parent ]
[ Parent ]
[ Parent ]
MySQL has taken a bigger share of the market, and this is beginning to show in the development cycle. For example the text searching features in MySQL are there by default and works okay(ish). Postgres has this as an add-on, but it is a bit more work, for what looks like a more flexible system.
If you are writing an application for others to use, or to share (I hope you are), I think MySQL is the way to go if it is a website based thing simply because practically every webhost supplies MySQL, Postgres is more hit and miss.
If it is something in house, or where someone would set up a database especially, then I'd go Postgres most times (it has more "Tao of programming", smaller, cleaner, probably less featured, but you probably don't care about the missing features - but do check that is true before you start!).
[ Parent ]
"If it is something in house, or where someone would set up a database especially, then I'd go Postgres most times (it has more "Tao of programming", smaller, cleaner, probably less featured, but you probably don't care about the missing features"
Not sure I follow you there -- PostgreSQL has far more features than MySQL (although, to be fair, the gap reduces with every major release of MySQL), and those features they do have in common, are usually more mature in PostgreSQL.
If it's a matter of learning and teaching yourself about DB's, then rather go for Postgres, as it's a true, bonafide, stable, mature, DMBS, and most of what you learn from it will be applicable to MySQL (with some tweaking) -- they same cannot be said of doing things the other way around...
Cheers.:wq
[ Parent ]
* Atomicity states that database modifications must follow an all or nothing rule. Each transaction is said to be atomic. If one part of the transaction fails, the entire transaction fails. It is critical that the database management system maintain the atomic nature of transactions in spite of any DBMS, operating system or hardware failure.
* Consistency states that only valid data will be written to the database. If, for some reason, a transaction is executed that violates the database's consistency rules, the entire transaction will be rolled back and the database will be restored to a state consistent with those rules. On the other hand, if a transaction successfully executes, it will take the database from one state that is consistent with the rules to another state that is also consistent with the rules.
* Isolation requires that multiple transactions occurring at the same time not impact each other's execution. For example, if Joe issues a transaction against a database at the same time that Mary issues a different transaction, both transactions should operate on the database in an isolated manner. The database should either perform Joe's entire transaction before executing Mary's or vice-versa. This prevents Joe's transaction from reading intermediate data produced as a side effect of part of Mary's transaction that will not eventually be committed to the database. Note that the isolation property does not ensure which transaction will execute first, merely that they will not interfere with each other.
* Durability ensures that any transaction committed to the database will not be lost. Durability is ensured through the use of database backups and transaction logs that facilitate the restoration of committed transactions in spite of any subsequent software or hardware failures.
[ Parent ]
Several without any priority, mayby HSQLdb most since doing a lot of J2EE development (its easy to configure), but also MySQL, firebird2 and sqlite (Python TurboGears). So voted for 'other'.
[ Parent ]
Besides that I'm using sqlite and firebird at home to test my apps.
[ Parent ]
[ Parent ]
[ Parent ]
Reads are lightning fast -- I once clocked 100,000+ reads per second on a three way table join which just about blew my mind. (The dataset had already been read at that point so was sitting nicely in Linux's cache).
Writes (at least in the default 'safe' ACID complient mode aren't the fastest, but in the web world writes are relatively uncommon, even on interactive apps like forums).
But the best part? Administration is a doddle -- expecially doing remote backups (1000+ databases on a box? No problemo).
The only time we switch to a 'big iron' database (we like PostgreSQL, but there's not much in it anymore) is if we have a client with a big (read 1GB+) dataset. We're not silly enough to store binaries in our database so that hardly ever happens (maybe we just need bigger clients... :-)
[ Parent ]