I think some of the confusion of tblview is that it has two meanings. In the SELECT usage of the "view" part, one has the creation of a big flat table from multiple tables. Where as, when view is used with UPDATE the view is a subset of a single table. If viewtbl (meaning view or subset of a single table) or something different than tblview were use with UPDATE, then the confusion could be avoided. RRR
Bill Downall wrote: > > Konstantin, > > My SQL Instant Reference (SQL 92) says: > > "The principle is that an insertion of or change to one row in the view > must translate to an insertion of or change to one row in the leaf > underlying table." > > and > > "The specific conditions outlined in the standard for a view to be > updatable are these: > > *) It must be drawn on one and only one simply underlying table. In > other words, no joins." > > It goes on for 6 more bullets. It does say later "some products may > relax [these restrictions]," but if R:Base decided to, I lost track of that > change. > > Bill > > On Thu, 20 Dec 2001 22:14:25 +0000, K G wrote: > > >Any view built from several-correlated table can be UPDATEABLE. In > your > >case, this is updateable view, > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
