Functionality in database or external langauge

From: Dennis Gearon <gearond(at)fireserve(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Functionality in database or external langauge
Date: 2004-05-13 03:33:59
Message-ID: 40A2ECA7.40705@fireserve.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'd like to get people's feelings about the topic.

At one extreme is to use table locking and external language queries to
even do referential integerity - a la Old (present?) MySQL/PHP.
A more realistic low end is to use Postgres or something more towards
heavy iron (if necessary) and use referential integrity, data integrity,
check cababilities.

At the other end is to only allow access to normal operation of the
database via procedures for only predefined operations on the data, with
different levels of authority in different scripts with different users.

It is a lot easier to change databases is the functionality is in the
external langauge. Both the access and the data integerity and business
rule enforcement is a lot better with only procedure access.

What's everyone's experience with these paradigms?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeffrey W. Baker 2004-05-13 04:31:43 Re: pg_xlog becomes extremely large during CREATE INDEX
Previous Message Tom Lane 2004-05-13 03:18:41 Re: pg_xlog becomes extremely large during CREATE INDEX