Re: why postgresql over other RDBMS

From: "Alexander Staubo" <alex(at)purefiction(dot)net>
To: "Ron Johnson" <ron(dot)l(dot)johnson(at)cox(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: why postgresql over other RDBMS
Date: 2007-05-24 17:48:40
Message-ID: 88daf38c0705241048l42296d4bra57ccdccaa754f99@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 5/24/07, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> wrote:
> > [2] Nobody else has this, I believe, except possibly Ingres and
> > NonStop SQL. This means you can do a "begin transaction", then issue
> > "create table", "alter table", etc. ad nauseum, and in the mean time
> > concurrent transactions will just work. Beautiful for atomically
> > upgrading a production server. Oracle, of course, commits after each
> > DDL statements.
>
> Rdb/VMS and CODASYL DBMS (both Oracle, formerly DEC, products) also
> have transactional DDL.

Not exactly mainstream databases, and Codasyl isn't even a relational
database as far as I remember.

> Interbase/Firebird probably also has transactional DDL.

Apparently. I'm surprised, given how InterBase and Firebird otherwise
feel so awfully ancient.

All right, so not unique, but very rare.

Alexander.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Erik Jones 2007-05-24 17:57:34 Re: why postgresql over other RDBMS
Previous Message Ericson Smith 2007-05-24 17:28:21 Re: why postgresql over other RDBMS