`0.6.0` Includes with multiple `toArray` fails

[boyswan]

• [ x ] I've validated the bug against the latest version of DB packages

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

export const myCollection = createLiveQueryCollection({
  getKey: x => x.id,
  query: q => q
    .from({ tf: parentCollection })
    .select(({ tf }) => ({
      id: tf.id,
      nodesA: toArray(q
        .from({ n: flowCollection })
        .where(({ n }) => eq(n.id, tf.flow_id))),
      nodesB: toArray(q
        .from({ n: flowCollection })
        .where(({ n }) => eq(n.id, tf.flow_id))),
     ...

Both nodesA and nodesB should be an array of 1 item.

In the example above I get:

{
    "id": "e31ac544-9b50-4324-baa5-b4c836ed4cee",
    "nodesA": [ { ... } ],
    "nodesB": [],  <------ missing data
    "$synced": true,
    "$origin": "remote",
    "$key": "e31ac544-9b50-4324-baa5-b4c836ed4cee",
    "$collectionId": "live-query-7"
}

If I remove nodesA from the query, I get:

{
    "id": "e31ac544-9b50-4324-baa5-b4c836ed4cee",
    "nodesB": [ { ... } ],
    "$synced": true,
    "$origin": "remote",
    "$key": "e31ac544-9b50-4324-baa5-b4c836ed4cee",
    "$collectionId": "live-query-7"
}

[kevin-dp]

Hi @boyswan,

I tried reproducing the bug you're describing but i did not manage to reproduce it. Both arrays are always populated. Could you please provide a complete reproducible example.

[boyswan]

Tested again with newest versions and is working now. I think in my case it was actually related to #1432 - the toArray was a bit of a red herring.