Difference between TUPLE and a look up table

[Former Member]

Hi all,

As we all know, there is a new data type called "TUPLE" that has been introduced in MDM 7.1.

can u please explain me the difference between a TUPLE and a look up table ?

when a field is declared as a tuple, where the structure of tuple is stored? is that in a separate table or the main field itself?

how does tuple effect the performance compared to lookup tables?

Thanks in advance,

Sravan Velamury

[Former Member]

Hi Sravan,

You can "effectively" compare a tuple to a lookup table where all possible combinations of tuple member field's values are filled out. A tuple item in this case can be represented as a member of the Cartesian product of the tuple's fields value set.

Again, if a tuple has field "A" and field "B", the former (A) with for example 7 possible value and the latter with 16 possible value, then you could theoretically represent this tuple with a lookup table with the same field set: all possible combinations of values of "A" and "B". The lookup table should have then 7*16 entries.

Hope this helps to show the relationship of them.

Regards,

Balázs

[Former Member]

Hi Sravan,

You can compare Tuple with the Qualified table, for each record it creates a separate instance unlike lookup table which is common for all the records and as stated above tuple can be nested to any level(theorotically infinite) and can include all type of structures like lookup, qualified and tuple as well.

We create Tuples in the console itself as we normally create lookups and then linked the tuple with the field of main table.

Regards,

Jitesh Talreja

[Former Member]

Tuple is just an structure; we cant compare the same either with lookups or attributes; since lookups and attributes physially store their possible values.

Jitesh : Am not sure that you can include qualified or taxonomy into Tuple.

thanks.

[Former Member]

Hi,

MDM tuples are a basic, all-purpose data modeling building block thathave many uses and capabilities for structuring and storing MDM data.

Tuples that include lookups subsume, extend, and generalize other specialized MDM structures such as qualified lookup tables and parent/child relationships.

The most notable feature of tuples is that they allow you to create nested structures, including deeply nested multi-level structures of arbitrary depth, with a one-to-many relationship at every level.

A tuple field does not represent a single data value, but rather an entire subrecord (or set of subrecords) that belongs exclusively to its parent record. The value of this subrecord is the combined values of the tupleu2019s member fields, including both its display and non-display fields.

hope this may help you.

Regards,

srinivas

[Former Member]

Hi Sravan,

Tuple is a newly introduced data type.

It is something very much physical and hence stored in db memory.

A tuple may be a structure comprising of a collection of simple data types like test, integer, boolean or it may also be as complex as a field in tuple to be a tuple itself ie. nested tuple.

Difference between look up and tuple is a lookup can be a field of tuple whereas the other way round is not possible.

Refer https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/206fed62-b48b-2b10-70b0-f12a99b9...

Hope it helps.

Thanks,

Minaz