Lists are currently limited to primitives while sets are currently limited to entities. The MySQL support for tree-ware lists is to store the entire list as a single value without support for adding, modifying, or deleting individual elements in the list. Lists are also hard to change in a backward compatible fashion. For example, you may start with a list of primitive values but later on you may want to store more information in each element of the list. While this kind of migration can be added, the new API for accessing the model will not be backward compatible with the old API because of the difference in representation of the elements. Novice users may not worry about future changes and choose lists instead of sets to represent (some of) their collections. Having both lists and sets also complicates the implementation of tree-ware. So it is better for everyone if lists are dropped and only sets are supported.
Lists are currently limited to primitives while sets are currently limited to entities. The MySQL support for tree-ware lists is to store the entire list as a single value without support for adding, modifying, or deleting individual elements in the list. Lists are also hard to change in a backward compatible fashion. For example, you may start with a list of primitive values but later on you may want to store more information in each element of the list. While this kind of migration can be added, the new API for accessing the model will not be backward compatible with the old API because of the difference in representation of the elements. Novice users may not worry about future changes and choose lists instead of sets to represent (some of) their collections. Having both lists and sets also complicates the implementation of tree-ware. So it is better for everyone if lists are dropped and only sets are supported.