Fixed conflict for createdAt and __v when doing update or findOneAnd…

[abhijitborade]

This is patch for Issue #46.
MongoError: Updating the path 'createdAt' would create a conflict at 'createdAt'

[stefanwalther]

Any plans to merge this?

[abhijitborade]

@drudge Please review and merge this pull request.

[surfer77]

When can this be merged ? getting the same error.

[abhijitborade]

I don't think @drudge is active. So I have published this fork separately as mongoose-timestamp2.

[developdeez]

@abhijitborade simply replacing mongoose-timestamp with mongoose-timestamp2, still had the error for me. Maybe I missed something?

[abhijitborade]

@abhijitborade simply replacing mongoose-timestamp with mongoose-timestamp2, still had the error for me. Maybe I missed something?

@developdeez, can you share your query?

[developdeez]

@abhijitborade simply replacing mongoose-timestamp with mongoose-timestamp2, still had the error for me. Maybe I missed something?

@developdeez, can you share your query?

 await User.findByIdAndUpdate(id, {
                $set: myUser
              });

[abhijitborade]

@developdeez I got it fixed. Check this issue in mongoose-timestamp2.

[developdeez]

@abhijitborade awesome. I'll check it out asap. thanks :)

[dmackinn]

@drudge Any chance this could get merged into the main package? Are you still maintaining this? A good number of people are still downloading and using this package.