Not using reference integrity tools (triggers, constrains) is in log-term a
very dangerous practice.
- you cannot protect your data against by-passing your software simply with
psql;
- the more sophisticated scheme you use the more error prone it is; I am
very sceptical to solutions where somebody says my software is so excelent
that it does not need reference constrains on server basis and I had so many
problems with putting my software working with reference constrains that I
had to remove them. First question that I have is: does that guy really
understand referencial integrity introduced by his software.
Andrzej Mazurkiewicz
> -----Original Message-----
> From: marten@feki.toppoint.de [SMTP:marten@feki.toppoint.de]
> Sent: 23 listopada 1999 10:42
> To: sbirch@ironmountainsystems.com
> Cc: pgsql-general@postgreSQL.org; pgsql-novice@postgreSQL.org
> Subject: Re: [GENERAL] Re: Is PostgreSQL ready for mission
> criticalapplications?
>
>
> And to mention, how different the expectations are: some persons out
> there mentioned, that referential integrity would be a very urgent need
> for them - I've the totally different opinion about this:
>
> When doing procedural queries to the database, this need is ok. If you
> put a full oo->rdbms wrapper on top of this database and do your
> programming in some oo-languages this need vanishes - because referential
> integrity does so much in the background, that your object-model in
> your application simply becomes wrong - therefore I throw away
> referential integrity. It makes the administration for the databases
> also much more simplier.
>
> Just my opinion .. not to be misinterpreted. I encourage every work
> the people push into PostgreSQL because I want to have a free
> database.
>
>
> Marten
>
>
>
>
>
>
>
> ************
