| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alexey Klyukin <alexk(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Another proposal for table synonyms |
| Date: | 2010-11-30 20:05:07 |
| Message-ID: | 4CF558F3.8070907@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alexey,
> Here is the proposal to add synonyms to PostgreSQL. Initial goal is to add synonyms
> for relations (tables, views, sequences) and an infrastructure to allow synonyms
> for other database objects in the future.
Can you explain, for our benefit, the use case for this? Specifically,
what can be done with synonyms which can't be done with search_path and
VIEWs?
I ask partly because I've migrated some Oracle databases to PostgreSQL,
and did not find replacing the functionality of synonyms to be at all
difficult. Presumably you've run into a case which was difficult?
BTW, I have a specific use case for *column* synonyms which isn't
currently covered by our existing tools.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-11-30 20:09:31 | Where are we on Standby Promotion? |
| Previous Message | Yeb Havinga | 2010-11-30 19:57:39 | Re: Fix for seg picksplit function |