Updateable views. This is great. I didn't know about these. Absolutely delicious ! I found a great example here... http://vibhorkumar.wordpress.com/2011/10/28/instead-of-trigger/
The problem of user updating >1 alias remains, but I have no problem bouncing them if they attempt that. Maybe return a "-E- You cannot update multiple aliases of the same base value" (something like that). I'd just have to detect this circumstance, raise the message and bounce (return OLD). Does this sound doable? -----Original Message----- From: Craig Ringer [mailto:ring...@ringerc.id.au] Sent: Thursday, August 23, 2012 9:52 AM To: Gauthier, Dave Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Can column name aliases be supported? 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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
