Re: Database-valued attributes?

From: Marshall Spight <mspight_at_dnai.com>
Date: Wed, 12 Nov 2003 16:28:21 GMT
Message-ID: <Fctsb.183266$e01.661529@attbi_s02>

"Paul Vernon" <paul.vernon_at_ukk.ibmm.comm> wrote in message news:bot382$ops$1_at_gazette.almaden.ibm.com...

> OK. So possible representations are really rather like tuple types.
> Personally, I can't see why we can't define them as such. I guess Bob will
> tell me why not. ;-)

Funny you would mention that. I was just thinking about the same thing.

So: what is the *logical* difference between a tuple with int x, int y and a scalar with int x, int y? Yes, the scalar is encapsulated, but all that really means is that its implementation is free to be whatever it wants, as long as it conforms to the interface. In other words, saying something is a scalar is making a statement about its implementation, *not* about its logical properties.

I can't think of any *logical* differences between a scalar and a tuple.

Marshall Received on Wed Nov 12 2003 - 10:28:21 CST