| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can column name aliases be supported? |
| Date: | 2012-08-23 13:52:03 |
| Message-ID: | 50363583.8060608@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/23/2012 09:32 PM, Gauthier, Dave wrote:
> The view approach for queries is workable, at least for queries. Thanks for the input on that and the idea to replicate the various aliases in the view!
The key issue with all your approaches is whether the client can ever
`UPDATE` the view. If they can, and you duplicate the column under
multiple aliases, what happens when they `UPDATE` two of the aliases to
different values?
> I too would like to shoot the clients. But as they say, the customer is always right !
Heh, I wouldn't shoot them. Fire the client means:
http://sixrevisions.com/project-management/how-to-fire-bad-clients/
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2012-08-23 14:09:40 | Re: At what point does a big table start becoming too big? |
| Previous Message | Martin French | 2012-08-23 13:51:19 | Re: At what point does a big table start becoming too big? |