Re: which database to use?
| From: | Doug Semig | Date: | Thu, 10 Aug 2000 20:24:16 +0000 |
| Subject: | Re: which database to use? | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-1943@lists.php.net to get a copy of this message | ||
Actually, the powers that be at MySQL have announced MaxSQL. It's (from
what I gather...I could be wrong) MySQL with transaction support provided
by Berkeley DB (from Sleepycat). You might want to look at that since
you're already familiar with MySQL.
But PostgreSQL and Interbase will provide much more than just transaction
support. They support advanced features such as views, triggers, and
stored procedures (I **think** both support stored procedures, anyway).
MySQL has no support for these kinds of features (yet!...they're furiously
developing MySQL!).
I know that PostgreSQL has a hard-coded row size limitation of 8k that you
can usually increase to 32k at compile-time. I do not know if IB has any
such limitation.
If I remember correctly, IB has been using multi-version concurrency
control (instead of table/row locks...speeds things up) since its
inception, while MVCC is relatively new in PostgreSQL.
Sounds like I am pro-interbase, huh? Actually, I use PostgreSQL.
Remember, interbase just recently opened the source. Oh, they announced
that it would be opensource half a year ago...but it didn't actually happen
until very recently.
Just rambling and giving you some things to think about...
Doug
Marvin was heard at 09:28 AM 8/10/00 -0400 to say:
>I'm looking for a database with transaction support. I'm currently using
>MySql in some applications. I know they're coming out with this feature
>later in the year.
>
>The 2 candidates I'm looking at are PostgreSQL and Interbase. PostgreSQL has
>been around for a while and Interbase is a newcomer to the field. Any
>recommendations?