From: | "K(dot)T(dot)" <death(at)solaris1(dot)mysolution(dot)com> |
---|---|
To: | "Scott Alexander" <scott(dot)alexander(at)mindspring(dot)com>, <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] Newbie questions |
Date: | 1999-06-09 05:33:14 |
Message-ID: | 000e01beb239$92b3f5e0$2b9264d1@p2-400-death |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
From: Scott Alexander <scott(dot)alexander(at)mindspring(dot)com>
To: pgsql-general(at)postgreSQL(dot)org <pgsql-general(at)postgreSQL(dot)org>
Date: Tuesday, June 08, 1999 5:57 PM
Subject: [GENERAL] Newbie questions
>Database design - CASE tools
>============================
>For people who *don't* use a CASE tool: what do you find to be the most
>efficient method of defining your database schema?
The lack of user friendly interfaces is one of the reasons why I choose not
to develop large (> 60 tables) databses in PostgreSQl...but when I do
develop I simply save the SQL stmts in a text file so I can reuse them to
recreate the database at any time.
>Additional SQL features
>=======================
>referential integrity, and automatic two-phase commit. (Borland's
>Interbase 5.5 is a good example which incorporates all these features.)
Ugg Interbase :) Lets not go there :)
PostgreSQL supports Triggers, Stored Procedures, Rollback, and autocommit.
Referential Integrity is not yet working. I leave it to others to itemize
all the other nifty features :)
From | Date | Subject | |
---|---|---|---|
Next Message | mascarim | 1999-06-09 06:32:45 | |
Previous Message | Scott Alexander | 1999-06-08 22:51:36 | Newbie questions |