| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Medi Montaseri <montaseri(at)gmail(dot)com> |
| Cc: | s(dot)borse(at)direction(dot)biz, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: synonym |
| Date: | 2007-12-17 02:10:30 |
| Message-ID: | 200712170210.lBH2AUJ11224@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Medi Montaseri wrote:
> PostgreSQL does not support SYNOSYM or ALIAS. Synonym is a non SQL 2003
> feature implemented by Microsoft SQL 2005 (I think). While it does provide
> an interesting abstraction, but due to lack of relational integrity, it can
> be considered a risk.
>
> That is, you can create a synonym, advertise it to you programmers, the code
> is written around it, including stored procedures, then one day the backend
> of this synonym (or link or pointer) is changed/deleted/etc leading to a run
> time error. I don't even think a prepare would catch that.
>
> It is the same trap as the symbolic links in unix and null pointers in
> C/C++.
It is on the TODO:
* Add support for public SYNONYMs
http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pino Martínez Herbut | 2007-12-17 14:53:03 | Ayuda Postgre |
| Previous Message | Tom Lane | 2007-12-16 23:57:07 | Re: reading pg_stat_activity view |