It doesn't. Pick is not relational. I was just showing a mapping between
the relational model and Pick's physical model, thereby exposing a weakness
in the physical model. To preserve "PK persistence" as you call it, one
would need to actually have a PK for the MV columns. This would be
problematic, since it's really a collection of MV columns synchronized
together that form a nested relation, and Pick itself doesn't know about the
multi-column association; it's up to the application to maintain this.
"Database Guy" <dbguy101_at_hotmail.com> wrote in message
news:7fdee71c.0311081524.77d4fc78_at_posting.google.com...
> davebest_at_usa.net (Dave Best) wrote in message
> >In Pick, the primary key of a MV element is the primary key
> > of the record plus its array index.
>
> Really? So how does PK persistence work when you insert or delete
> values in the array?
>
>
> DG
Received on Sun Nov 09 2003 - 14:35:45 CST
