dbTalk Databases Forums  

Date and McGoveran comments on view updating 'problem'

comp.databases.theory comp.databases.theory


Discuss Date and McGoveran comments on view updating 'problem' in the comp.databases.theory forum.



Reply
 
Thread Tools Display Modes
  #271  
Old   
Brian Selzer
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-15-2008 , 04:13 PM







"paul c" <toledobythesea (AT) oohay (DOT) ac> wrote

Quote:
Brian Selzer wrote:
"paul c" <toledobythesea (AT) oohay (DOT) ac> wrote in message
news:Wve%k.3357$yK5.661 (AT) edtnps82 (DOT) ..
... Also, you appear to be laboring under the
delusion that relational algebra somehow includes relational assignment.

I feel no such weight on top of me because I know of no such thing as
'relational assignment', rather there is language assignment. My focus is
algebraic as I'll try to explain later, but as far as that I would agree
that the D&D A-algebra that I'm familiar with has no such thing as
'language assignment'. I don't think I ever said otherwise. I think
Date's Assignment Principle is simply a test for whether a language's dbms
respects the algebra it's premised on.
Perhaps I was reading too much into your post.




Reply With Quote
  #272  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM






Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #273  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #274  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #275  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #276  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #277  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #278  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #279  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
  #280  
Old   
paul c
 
Posts: n/a

Default Re: Date and McGoveran comments on view updating 'problem' - 12-17-2008 , 10:29 AM



Bob Badour wrote:
....
Quote:
A more important question is: How would one write a constraint that
deletes from SP ^ S affect SP but not S?
...
Using a typical relational algebra, my guess is that it would be
extremely lengthy, much longer than enumerating all the domains
involved. Eg., a disjunction with N-1 <OR> operations where N is number
of possible base headings multiplied by the number of possible
combinations of tuples in those relations, multiplied again by at least
three (since there are nominally three relations involved)! So, I don't
think it is a practical question as far as the RM as I know it is concerned.

Some language notation could be a shorthand for this, eg., S' = S might
mean that an S relvar can never be deleted from nor inserted to. One
might resort to a kind of catalog expression to establish some kind of
prototypical delete form where S' NOTEQUAL S MINUS X and X stands for
any possible relation, ie., any possible MINUS operand. But I'd say the
question is outside the realm of the algebra and therefore out of the
realm of the calculus (even though I know very little of the calculus).
Maybe if the RM admitted recursive structures, some algebra could
handle it and therefore some kind of terse algebraic constraint might be
possible.

Just guesses ...


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.