Relationship values may be saved with the wrong order

Following on from #1359, and @mitchellhamilton’s comment regarding this API suggestion from @jesstelford:

return {
  disconnectAll: true,
  connect: ids.map(id => ({ id })),
};

Just tried that and it changes the order of the items which would probably be really confusing for users

Since that API is currently our recommended way of “setting” the value of a relationship field, we should ensure it works as expected and saves the items in the given order

[willmatos]

Have any decisions been made on this? I have a scenario where I am trying to create a Playlist. In this scenario the order is everything.

[jhohlfeld]

Hi, I landed at this issue after initially setting up keystone and going through the getting started tutorial. After some instant success I am now stuck on exactly this issue.

This thread (https://stackoverflow.com/questions/66034621/keystonejs-user-defined-order-for-relationship) talks about using another intermediate list: make a list to describe the sorting order of the relation between two other lists (many to many). This however feels awkward and I would like to ask if this is still the only way to get sorting order within relationships?

I would prefer not to add a hook or some hacky SQL to reach my goal.