DataDeploy - UDS question..

FurnaceFace

Solaris 2.9
TeamSite 6.5 - SP2
OpenDeploy/DataDeploy 6.1

Hello,

In our system we want to use UDS and we have multi-value selects on our tagging UI. What is the best practice for putting out the values into the User Defined Schema? Should we create linked tables so we can represent each selection in the multi selection as a row or should we put all values into one field but have a delimiter separating them?

My database sense tells me that the former is the proper way but I would like to know what the recommended way is. How much customization is involved with creating the linked tables versus cramming the data into one field?

Thanks,
/FF

jed

In our system we want to use UDS and we have multi-value selects on our tagging UI. What is the best practice for putting out the values into the User Defined Schema? Should we create linked tables so we can represent each selection in the multi selection as a row or should we put all values into one field but have a delimiter separating them?

Shudder. All field values should not go into one column with a delimiter. E. F. Codd is rolling in his grave right now

See below. This would support many multi-select lists.

main_data
oid|path|title|description

111|file1|my title2|my description
112|file2|my title2|my description 2

main_data_multi
oid|name|value

111|states|ca
111|states|fl
111|states|me
111|cars|bmw
112|states|mx
112|cars|toyota
112|cars|ford
112|cars|yugo

How much customization is involved with creating the linked tables versus cramming the data into one field?

Minimal work should be needed for this. I do not have any sample configs handy, but there is a "list-to-replicant" option which will help support this. (I forget the exact syntax/name right now.)