Re: One Ring to Bind Them

In message <IbHDc.119764$HG.109138_at_attbi_s53>, Bill H <wphaskett_at_THISISMUNGEDatt.net> writes
>Marshall:
>
>"Marshall Spight" <mspight_at_dnai.com> wrote in message
>news:GipDc.159689$3x.28156_at_attbi_s54...
>>
>
>> Yes, it understands the meaning of this, so it knows what
>> a one-to-many relationship means. Does it have any other
>> facilities for understanding meaning? It can do
>> ON DELETE CASCADE but can it do ON DELETE
>> RESTRICT? Can it handle and understand many-to-many
>> relationships? Can it understand and enforce arbitrary
>> constraints a la SQL's CHECK? (These are actual questions,
>> not rhetorical ones; I'm not that familiar with MV.)
>
>Of course it does, and can. Remember it is both a datastore and an
>application environment wrapped into one. So, whatever needs to be done can
>be done. It is simply that this additional functionality is stored in the
>datastore too. Most of the MV products can even understand and cope with
>SQL functionality.

Thanks Bill. Not knowing what ON DELETE RESTRICT means, I couldn't really respond ...
>
>Like I said before, this is not to say that the MV model does
>everything...as nothing can. But it provides an interesting confluence of
>tools and capabilities that render the model very useful in solving business
>problems for many people and businesses.
>

Well, it can't actually *do* ON DELETE CASCADE (in native mode anyway) - it's just that what it can do has the same effect :-) As Bill says, it's *just* *different*

Cheers,
Wol

-- 
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999