On Thu, 01 Jul 2010 14:22:42 +0100
Simon Verona <[email protected]> wrote:
Jim
I did point out that my approach wasn't the "correct" approach, but
it works well for us.
I wasn't particularly criticizing your data forms, or anyone else's -
just pointing out that most people seem to think that they must use
multivalues because it is a multivalue database, but attributes are
generally the more correct form.
We use this technique quite a lot in our system, and it allows easy
extensibility. I guess if you wanted it to be "pure" you would have
an associated attribute with the descriptions in eg :
<1> Home]Work]Mobile
<2> 01142111111]08456862300]0784546564654
No, this is still wrong (in fact it is probably more wrong as you now
asking for a guaranteed order from two attributes and not one).
Associated values just mean that the value at MV n in attribute n is
associated with the value at MV n in attribute ~n
So, your example would be fine so long as you don't regard MV 2 as any
different from MV 1 (as in the type of the phone number is always
irrelevant - attr 1 is just a description without meaning other than
for presentation. Sometimes that would be valid, but usually you want
to programmaticly distinguish these (as in they are different
entities).
All we do is keep the contents of <1> in a seperate item stored
once.
I guess the fact that MV doesn't enforce a rigid database structure
is good, but also a noose to hang yourself with... Maybe I'm due for
hanging <G>
Jim - I missed my Wimbledon ticket - did you send it to the right
address??
Only cool people are allowed in to Wimbledon... so I will sneak in
round the back. See me on TV tomorrow.
Jim
--
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
