Best practive / help

[fransyozef]

Not really an issue but more help. I'm a bit confused.

db.rel.save('author', {
  name: 'George R. R. Martin', id: 1, books: [6, 7]
}).then(function () {
  return db.rel.save('book', { title: 'A Game of Thrones', id: 6, author: 1});
}).then(function () {
  return db.rel.save('book', {title: 'The Hedge Knight', id: 7, author: 1});
}).catch(console.log.bind(console));

what I don't understand in this code, you save a new author, and also add the new book foreignkeys. But in real life you would not know these keys before you created the book records. The author foreign key makes sense in the book records. So why the book id's in the 'books' array?

[luca147]

I can not find a way for this library to work properly, I am already thinking about making the relationships manually using pouch only.

[509dave16]

@fransyozef With the way that CouchDB/PouchDB, works there are no auto-incrementing IDs like a SQL database. In PouchDB, you can opt to have an _id generated for you(a uuid I believe). This is how you would have the ID ahead of time. And since uuid's are pretty much guaranteed to to be unique you shouldn't have to worry.

You can choose to have your HasMany relationships not represented by an array of IDs on the parent type. Take a look at this section of the README.md: https://github.com/pouchdb-community/relational-pouch#dont-save-hasmany. For this case you would first create the author and then create each book utilizing the id from the author you created.

If you would like I can come up with a code sample for you. The code sample you are referring to is following a pattern where child books that belong to the author are having their IDs stored on the author, whichh is not required. Just simply an example of how relational-pouch can be used.