domasx2/sequelize-fixtures — pull request #4 by ajfisher (2014-01-28 06:14:29+00:00)
Title: Some objects appear to get cached when they are associated

When creating a reasonable sized fixture I was finding that the objects returned in the promise as a result of the .find() operation appeared to be consistent or else kept returning the first item specified in the database.

This may be a result of a change in Sequelize 2, something to do with sqlite (what I'm using to test) or the vagaries of my specific objects.

This change allows an ID number to be specified as an alternative to an object as an option for association. This forces the .find(val) to return the specific instance each time and doesn't run into the same problems as before.

Of course this doesn't fix whatever the underlying issue may be but that appears to be out of the skills of by debugging / tracing capability with Node.