Re: multi-valued field?

In article <5ari90$o1q_at_engnews2.Eng.Sun.COM>, tvuong_at_Eng.Sun.COM writes:
>
> Steve,
>
> I do have a application similar to that being used by Kevin. Just
> say that the design step involving the choice of data modeling has
> already been performed by both the design and the spec team, and
> the final choice is to implement a multi-valued field as above.
> (In fact, a major influence of the decision is performance, but
> let's not get into that topic in this discussion).

[ I'll talk about this in a subsequent post because Steve is right on   the money and you are seeing examples of what happens when you embed   intelligence in your data ]

> Assuming now, that I have a column field that is multi-valued, one value
> is separate from another by a delimiter. For example, my rows
> might look like
>
> Record Multi-Values
> 1 a, b, c, d
> 2 a, b
> 3 d, e
> 4 b, c
>

Tony,

Take a look at the Sybase FAQ Q7.1/Q7.3... you should get some hints from the Encoded Characteristic Functions...

--
Pablo Sanchez              | Ph # (415) 933.3812        Fax # (415) 933.2821
pablo_at_sgi.com              | Pg # (800) 930.5635  -or-  pablo_p_at_corp.sgi.com
===============================================================================
I am accountable for my actions.   http://reality.sgi.com/pablo [ /Sybase_FAQ ]