ORM select query not working both ways

[jkemming]

I have an application with two tables named videos and producers respectively. The models are as follows:

nSQL('videos')
  .model([
    { key: 'id', type: 'int', props: ['pk', 'ai'] },
    { key: 'name', type: 'string' },
    { key: 'producerId', type: 'producers', props: ['ref=>videoIds[]'] }
  ]);
nSQL('producers')
  .model([
    { key: 'id', type: 'int', props: ['pk', 'ai'] },
    { key: 'name', type: 'string' },
    { key: 'videoIds', type: 'videos[]', props: ['ref=>producerId'] }
  ]);

It is a one-to-many relationship, that means each producer has many videos and each video has one producer. Inserting entries works like a charm, my test data looks as follows inside IndexedDB:

videos Table:

Key	Value
1	{ id: 1, name: "test1", producerId: 1 }
2	{ id: 2, name: "test2", producerId: 1 }
3	{ id: 3, name: "test3", producerId: 2 }

producers Table:

Key	Value
1	{ id: 1, name: "prod1", videoIds: [1, 2] }
2	{ id: 2, name: "prod2", videoIds: [3] }

Now I want to request an entry from the videos table with its respective producer in the result as follows:

nSQL('videos')
  .query('select')
  .orm(['producerId'])
  .where(['id', '=', 1])
  .exec();

The result however looks like this:

{
  id: 1,
  name: "test1",
  producerId: 1
}

If I try it the other way around it does work:

nSQL('producers')
  .query('select')
  .orm([videoIds'])
  .where(['id', '=', '1'])
  .exec();

The result is:

{
  id: 1,
  name: "prod1",
  videoIds: [
    { id: 1, name: "test1", producerId: 1 },
    { id: 2, name: "test2", producerId: 2 }
  ]
}

I already tried and tested a lot on my end but can't seem to find a bug in my application. Also, I copied and ran the example from the official documentation which gave the same results, meaning the author variable in that case was still the user id rather than the user object.

Am I doing something wrong or is there possibly a bug?

[only-cliches]

Just pushed v1.5.2, issue should be resolved.

Thanks for the heads up!

[jkemming]

Thank you very much for the quick fix, now everything is working as it's supposed to be!