Settings and activity
10 results found
-
0 votes
Anonymous
shared this idea
·
-
0 votesAnonymous
shared this idea
·
-
0 votesAnonymous
shared this idea
·
-
0 votesAnonymous
shared this idea
·
-
0 votesAnonymous
shared this idea
·
-
0 votes
An error occurred while saving the comment Anonymous
shared this idea
·
-
3 votesAnonymous
supported this idea
·
-
9 votesAnonymous
supported this idea
·
-
48 votesAnonymous
supported this idea
·
-
5 votes
An error occurred while saving the comment Anonymous
commented
That would even allow for proper DB nesting into each other, creating tree libraries.
An error occurred while saving the comment Anonymous
commented
It's like probability without replacement.
eg- I may make a DB for a food factory and thus have a library with fish, meat, vegetables. Another library with beef stick, carrot, tuna, chopped pork, onion. I want to arrange the second one into the first. So on meat field, I pick chopped pork and beef stick to link. When I edit fish field, I cannot pick (indeed they don't even show up on the list) chopped pork nor beef stick, for they are already linked.
Anonymous
shared this idea
·
Imagine the list of possible attributes is so big that it'd rather be made as a separate library and linked, not just items from a dropdown list field.