Qu: is it correct to assume implicit order preservation?

[thruflo]

Two questions relating to implicit ordering. I can obviously verify in code but I;m asking about this from a let's document the guarantee POV, partly so we don't accidentally change the behaviour:

1. Is there an implicit ordering to a collection, such as by insert time or key? For example when a live query doesn't have an orderBy. If so, does this work across synced and optimistic state?

2. Say I have a base collection that's ordered and then I derive a new collection / live query from it:

const { collection: orderedTodos } = useLiveQuery((query) =>
 query
 .from({ todo: todoCollection })
 .orderBy(({ todo }) => todo.inserted_at, 'asc')
)

const { data: pendingTodos } = useLiveQuery((query) =>
 query
 .from({ todo: orderedTodos })
 .where(({ todo }) => eq(todo.completed, false))
)

Is the second collection guaranteed to be in the same order as the first?

[samwillis]

If there is not orderBy in the query, there is no implicit order - it's essentially random.

(Technically, it likely in insertion order, but that's a side effect with zero guarantee)

[thruflo]

Got it 👍 good to know.

[justjake]

This is a bit awkward when it come to API responses w/ queryCollection. Many APIs return items in a natural order, and it's boilerplate to need to explicitly preserve that:

const popularPostsCollection = createCollection(
 queryCollectionOptions({
 queryKey: () => ["posts", "popular"],
 queryFn: () =>
 fetchPopularPosts().then((posts) =>
 posts.map((post, index) => ({ ...post, _index: index }))
 ),
 })
)
const postsWithAuthors = createLiveQueryCollection((q) =>
 q
 .from({ post: popularPostsCollection })
 .leftJoin({ author: usersCollection }, ({ post, author }) =>
 eq(post.author_id, author.id)
 )
 .orderBy(({ post }) => post._index, `asc`)
)