On Fri, Jan 23, 2009 at 5:32 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > Perhaps the right answer is to invent some new rule syntax to "redirect" > inserts/updates/deletes, say something like > > on update to foo do instead redirect to bar > > and then put some logic that's not so much different from what you've > got here into the rule engine itself ... or maybe better, just have the > rule engine automatically try to redirect if it's faced with having to > raise error for lack of a rule? It seems to me that the rule engine > has probably got all the infrastructure needed to convert the query the > way we'd like, we just don't have a suitable API to tell it to do that. >
and what about default values? if we redirect we will have to use the table's default (something i like) and AFAIU we won't have the ability to change it for the view at least not without manually create a new DO INSTEAD rule (something i don't like)... i'm missing something? or can we implement such "REDIRECT" with the ability to respect view's own defaults? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
