Skip to content

Issues: drudge/mongoose-timestamp

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 Open 17 Closed
11 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

updatedAt is not updating after any document get updated.
#54 opened Apr 4, 2024 by GautamSulok
1
various timezone
#51 opened May 17, 2020 by ali5991jalali
Timestamp Auto closed the TCP cause MongoNetworkError
#49 opened Aug 13, 2019 by kayac-chang
It is possible to have a configurable parameter?
#47 opened Aug 28, 2018 by carvalhoviniciusluiz
MongoError: Updating the path 'createdAt' would create a conflict at 'createdAt'
#46 opened Jul 23, 2018 by jonascasarin
2
Time to deprecate this package?
#45 opened May 27, 2018 by pronebird
Won't work with insertMany method
#44 opened Dec 4, 2017 by rrbe
2
created_at
#43 opened Sep 3, 2017 by mthomsit
1
Virtual createdAt not available on document.toJSON
#41 opened May 13, 2017 by Koka5
If createdAt or updatedAt is already present, ignore adding it
#31 opened Sep 8, 2015 by luckydev
When used with passport-local-mongoose and mongoDB 3.0 we get this issue
#29 opened Aug 21, 2015 by BrandonCopley
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.