On Fri, 2004-07-30 at 09:17, Secrétariat wrote:[color=blue]
> Hello !
> Why can't I update data when I use a VIEW instead of a TABLE ?[/color]
Because a view is not a table. Many views are inherently non-updatable,
and the backend assumes that all are.
[color=blue]
> How can I do similar action ?[/color]
Create a rule on the view to update the base table(s) instead.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Secrétariat wrote:
[color=blue]
> Hello !
> Why can't I update data when I use a VIEW instead of a TABLE ?
>[/color]
Why can't you drive home if you drink whisky instead of coca-cola?
Read the Manual Chapter 34 about the rule system.
Mage
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
On Fri, 30 Jul 2004, [iso-8859-1] Secrétariat wrote:
[color=blue]
> Why can't I update data when I use a VIEW instead of a TABLE ?
> How can I do similar action ?[/color]
We require explicit rules to be made for updating the view. Technically
there's a very small set of views for which we would need to make the
rules automatically to be spec complient, but those views are really
limited, IIRC, no joins, no group by, no set functions, no aggregates, and
some other limitations. It'd be nice to be able to handle more
complicated cases automatically, but it's non-trivial.
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
Comment