Problems with nested arrays

[ncirkel]

When calling some mutator methods on nested arrays (like collection.id.nested.array.0), the array is emptied.

After some debugging, I found the problem to be in /lib/index.js, line 326:
var arr = found && found[relPath];

The stored array is retreived, but not found: found['collection.id.nested.array'] returns null.

[acheron0]

I see the same thing, on the same line. Did anything come of this?

[IvanGaravito]

Hi, I got the same problem at my app when I started to use the racer-db-mongo plugin. Then after some debugging I figured out that this can be solved using the callback function when calling the mutator methods remove and insert and move, because the nested array is emptied and synced back to the Mongo DB, so before this happens you need to do the following:

  // Removing an item
  collection.remove(indx, function () {
    collection.set(collection.get())
  })

  // Inserting an item
  collection.insert(indx, obj, function () {
    collection.set(collection.get())
  })

  // Moving an item
  collection.move(from, to, function () {
    collection.set(collection.get())
  })

The push mutator only needs the nested array to be initialized to work alright.

  if (!collection.get()) collection.set([])
  collection.push(obj)

This not solves the problem, but keeps your app working.

[acheron0]

That did work. Thanks so much!

[bdoms]

I am currently experiencing something that seems like a related problem: I'm trying to subscribe within an array, and it doesn't work.

Doing model.subscribe('collection.id.nested.array') works fine and if I print out the array I can see all the data is there.

But doing model.subscribe('collection.id.nested.array.0') doesn't work at all. It returns an empty object, even when I know data is there.

What's funny is that this works fine with the in-memory data store, but as soon as I started using racer-db-mongo it started failing.