Re: (domain support) Re: theory and practice: ying and yang

On 1 Jun 2005 01:01:17 -0700, "DM Unseen" <dm_unseen_at_hotmail.com> wrote:

>I thought in most SQL DBMSses all SQL (result) sets are in fact (casted
>to) arrays, since they can contain duplicates

Multisets can contain duplicates.

> and have an (implicit)
>ordering even if you do not user order by (ROW_NUMBER/ROWID anyone?),

The SQL standard says that they must have an arbitrary order.

With SQL you can do this:

select * from select * from a

but you can not do:

select * from select * from a order by 1

Because you can select from a table variable but not from an array variable.

>Mailing internationally is often a must, but that does not make it any
>easier!

It is rather easy if you delegate the integrity checking to the users.

>Having a generalized international address (entity) that is just
>globally constrained is a real PITA, because this usually means
>one-size-does-not-fit-anybody.

An unlimited unicode string fits for almost anybody.

> Maybe using "dynamic" contstraints
>(based on country) would be a more interesting option.

It could be interesting for the most important countries for you, but I don't see anything dynamic in such constraints.

constraint x if Country = 'ES' then Numeric(5,0).TryParse(ZipCode, n)

Regards Received on Wed Jun 01 2005 - 16:41:18 CEST