Re: Another motivational example for inverse view

From: NENASHI, Tegiri <>
Date: Wed, 15 Nov 2006 17:06:17 +0100 (CET)
Message-ID: <Xns987C710B1479Aasdgba_at_194.177.96.26>

"Aloha Kakuikanu" <> wrote in

> Consider
> table PolarCoordinates (
> theta real,
> R real,
> )
> with constraints R>0, 0<=theta<pi
> view CartesianCoordinates
> select R*cos(theta) AS x, R*sin(theta) AS y
> from PolarCoordinates
> This view is clearly updateable, all we need to do is to apply inverse
> mapping to the any tuple inserted/updated/deleted.
> We can even write inverse view explicitly:
> view PolarCoordinates
> select sqrt(x*x+y*y) AS R, arcsin(y/sqrt(x*x+y*y)) as theta
> from PolarCoordinates

You are joking are you not ? It is simple because the structure of the relations is the same, there is not the change of the structure that a join of tables has, you did not create a new structure. The probleme of the view updatability is a morphing of one structure into the other.

Received on Wed Nov 15 2006 - 17:06:17 CET

Original text of this message