drudge / mongoose-timestamp Goto Github PK

View Code? Open in Web Editor NEW

310.0 7.0 64.0 64 KB

Adds createdAt and updatedAt date attributes that get auto-assigned to the most recent create/update timestamp

License: Other

JavaScript 100.00%

mongoose-timestamp's People

Contributors

Stargazers

Watchers

Forkers

nuxlli coen-hyde vizo smakinson mchapman inxilpro bick4ord jcugno jonlil apiaryio lourenzo snird almostagile hublo-co tangmonk kc-dot-io rujmah hellmagic lethalbrains sxyuan rfink jenshva theo-lubert runtitle saadullahaleem ionisx raja-sami-10p vecbralis imjerrybao floatinglomas hitoz juniordennis jovinbm lchenay mitchellporter tianyk linusbrolin zuijiaoluo sokardys codeofnode wongzigii jrobic integer-underflow lighthouse-io diablofong nanhapy wanmendaxue amitgehelot abhijitborade haipengz feidianbo leowin jarvisqj cuhuak bettinatee raziarch oats7777 soylemezali42 arun-thworks selfbriefs

mongoose-timestamp's Issues

It is possible to have a configurable parameter?

it is possible to disable a parameter so that it is not added?

for example:

mongoose.plugin(timestamps,  {
  createdAt: 'created_at',
  updatedAt: false
});

MongoError: Updating the path 'createdAt' would create a conflict at 'createdAt'

Last update on mongoose brings this message in all scheemas on my bd.

All Updates and insertions are bring this error... Any solution?

Indices for createdAt and updatedAt attributes

Is there any way of defining indices for createdAt and updatedAt attributes?

Timestamp Auto closed the TCP cause MongoNetworkError

I Worked with

"mongoose": 5.6.9
"mongoose-timestamp": 0.6.0

Do you want to request a feature or report a bug?
I want to report a bug.

What is the current behavior?
When I working with a long process task like transfer data from MySQL to Mongo Atlas.
I try so many time but finally I got this:

(node:74121) UnhandledPromiseRejectionWarning: MongoNetworkError: connection 2 to cluster0-shard-00-01-ug0nb.gcp.mongodb.net:27017 closed
    at TLSSocket.<anonymous> (/Users/kayac/Projects/Work/Backend_Server/node_modules/mongodb-core/lib/connection/connection.js:352:9)
    at Object.onceWrapper (events.js:288:20)
    at TLSSocket.emit (events.js:200:13)
    at net.js:586:12
    at TCP.done (_tls_wrap.js:479:7)

And My config like this:

    const db = await mongoose.connect(path, {
        useNewUrlParser: true,
        socketTimeoutMS: 600 * 1000,
        connectTimeoutMS: 600 * 1000,
        autoReconnect: true,
        keepAlive: true,
        reconnectTries: 30,
        poolSize: 20,
    });

socketTimeoutMSand connectTimeoutMS both doesn't help.

But I remove the

const timestamps = require('mongoose-timestamp');
Schema.plugin(timestamps);

And My task success.

Did mongoose timestamp auto close the TCP connection when process too long?

bson dependency not needed any more

Object function Date() has no method 'get'

When setting the names of the createdAt and updatedAt properties, I am getting the following error:

 node_modules/mongoose-timestamp/index.js:34
        .get( function () {
         ^
  TypeError: Object function Date() { [native code] } has no method 'get'
      at timestampsPlugin (node_modules/mongoose-timestamp/index.js:34:8)
      at Schema.plugin (node_modules/mongoose/lib/schema.js:570:3)
      at Mongoose._applyPlugins (node_modules/mongoose/lib/index.js:403:12)
      at Mongoose.model (node_modules/mongoose/lib/index.js:320:12)
      at NativeConnection.Connection.model (node_modules/mongoose/lib/connection.js:600:23)

This also appears to be the error that is causing the Travis tests to fail on the continuing integration server.

updatedAt not updated when i do some updated to document

when i do update to docement, field updatedAt not updated with current Date time.
example my query

User.findByIdAndUpdate(id, { last_login: new Date() }).exec()

Use new Date.now() vs new Date()

new Date() returns the server's time. You should use Date.now(), it returns the UTC time:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/now

various timezone

If i want to search in createdAt for specific timezone like Turkey timezone I have to convert it to uct?

Object function Date() has no method 'get'

When setting the names of the createdAt and updatedAt properties, I am getting the following error:

node_modules/mongoose-timestamp/index.js:34
.get( function () {
^
TypeError: Object function Date() { [native code] } has no method 'get'
at timestampsPlugin (node_modules/mongoose-timestamp/index.js:34:8)
at Schema.plugin (node_modules/mongoose/lib/schema.js:570:3)
at Mongoose._applyPlugins (node_modules/mongoose/lib/index.js:403:12)
at Mongoose.model (node_modules/mongoose/lib/index.js:320:12)
at NativeConnection.Connection.model (node_modules/mongoose/lib/connection.js:600:23)

This also appears to be the error that is causing the Travis tests to fail on the continuing integration server.

created_at

When used with passport-local-mongoose and mongoDB 3.0 we get this issue

[TypeError: Cannot assign to read only property 'checkKeys' of true]

passport-local-mongoose 1.0.1
timestamps 0.4.0

var mongoose = require('mongoose');
var passportLocalMongoose = require('passport-local-mongoose');
var timestamps = require('mongoose-timestamp');

var Schema = mongoose.Schema;

exports.User = mongoose.model('User', new Schema({
  username: {
    type: String,
    index: {
      unique: true,
      sparse: true
    }
  },
  email: String
}, {
  safe: true,
  strict: true
}).plugin(passportLocalMongoose, {}).plugin(timestamps));

removing the timestamps plugin gets this working, but I liked the timestamps plugin.

How could I add es_indexed:true from Mongoosastic

Awesome plugin!

Can I add an extra option to createdAt and updatedAt to index it? Thanks.

wish: allow customizing the name of the columns

Thanks for this plugin.

It would be nice if the column names 'updatedAt' and 'createdAt' could be customized.

In our case, we are considering adding it to an existing system where we already have a different naming convention established.

If createdAt or updatedAt is already present, ignore adding it

If a schema already has createdAt field, dont add it. Instead, add updatedAt field alone and maintain it. Vice versa for the updatedAt field.

Right now in version 0.3.0, this is the error I get when createdAt is already there and if I use mongoose-timestamp in that schema.

/Users/Anand/xyz/node_modules/mongoose-timestamp/index.js:34
      .get( function () {
       ^
TypeError: Object #<Object> has no method 'get'
    at timestampsPlugin (/Users/Anand/xyz/node_modules/mongoose-timestamp/index.js:34:8)
    at Schema.plugin (/Users/Anand/xyz/node_modules/mongoose/lib/schema.js:570:3)
    at Object.<anonymous> (/Users/Anand/xyz/models/session_token.js:12:20)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/Anand/xyz/models/agent.js:17:20)

`updatedAt` is not updating after any document get updated.

TypeError: documentSchema.plugin is not a function

did an npm install mongoose-timestamp, implemented the plugin, as follows:

var timestamps = require('mongoose-timestamp');
var mongoose = require("mongoose");

var mongoSchema = mongoose.Schema;

var documentSchema = {
    name: String,
 isPayed: { type: Boolean, default: false }
};

documentSchema.plugin(timestamps);
module.exports = mongoose.model('documents', documentSchema);

When starting node, the compiler returns folliowing error:

PS C:\Users\paul\Programming\cli\ngEstrich_Server> node server
C:\Users\paul\Programming\cli\ngEstrich_Server\models\documents.js:65
documentSchema.plugin(timestamps);
               ^

updatedAt not updated after findByIdAnd

Only works after save().
Was a mongoose limitation. Solved in mongoose 4. Please add support.

Global configuration/setup instead of by each model

First: Thanks!

Second: I tried to research about the ability to enabled timestamps 'globally'.
Is there a way to enable timestamps to the mongoose object?

like with promises:

let mongoose = require('mongoose');

mongoose.Promise = global.Promise;

Bug

I believe that line 31 should be using createdAt the variable, not "createdAt" the string

 if (schema.path('createdAt')) {

Retrive documents based on sort order for array of subdocuments

I have documents like below(i am using node.js and mongoose).

{                                                             
        "id" : 1,                                             
        "name" : "strs",                                      
        "subs" : [                                            
                {                                             
                        "sortorder" : 5,                          
                        "type" : "volvo"                          
                },                                            
                {                                             
                        "sortorder" : 2,                          
                        "type" : "benz"                          
                }                              
        ]                                                     
}                                                             
{                                                             
        "id" : 2,                                             
        "name" : "newname",                                   
        "subs" : [                                            
                {                                             
                        "sortorder" : 3,                          
                        "type" : "volvo"                           
                },                                            
                {                                             
                        "sortorder" : 1,                          
                        "type" : "benz"                           
                }                                    
        ]                                                     
}

When i query for subs.type: volvo , i need to sort the documents based on the sortorder for volvo. I want output like below.

{                                                             
        "id" : 2,                                             
        "name" : "newname",                                   
        "subs" : [                                            
                {                                             
                        "sortorder" : 3,                          
                        "type" : "volvo"                           
                },                                            
                {                                             
                        "sortorder" : 1,                          
                        "type" : "benz"                           
                }                                    
        ]                                                     
}     
{                                                             
        "id" : 1,                                             
        "name" : "strs",                                      
        "subs" : [                                            
                {                                             
                        "sortorder" : 5,                          
                        "type" : "volvo"                          
                },                                            
                {                                             
                        "sortorder" : 2,                          
                        "type" : "benz"                          
                }                              
        ]                                                     
}

Doesn't support nested keys

Correct me if I'm wrong, but this doesn't work:

Schema.plugin(require('mongoose-timestamp'), {
  createdAt: 'created.at',
  updatedAt: 'updated.at'
});

Virtual `createdAt` not available on document.toJSON

In earlier version 0.1.1 i was not specifying any createdAt in my schema file.
mongoose-timestamp used to add and and setupvirtuals

Now mongoose-timestamp is adding virtuals only if i have explicitly defined the createdAt field.

Won't work with `insertMany` method

It seems like this plugin does not support insertMany method because it won't call save hook.

And I find this issue #723 may be helpful...

Can you support this feature ？

Thanks.

Time to deprecate this package?

Hi,

It seems that mongoose has been supporting timestamps option for quite a while now. Is there any need to use mongoose-timestamp anymore or there is some sense to point people to mongoose docs and deprecate the module?

Thanks for all great work on this module, I've been using it for years and currently upgrading some of the old projects to use the latest mongoose, so that's how I stumbled upon this issue :)

http://mongoosejs.com/docs/guide.html#timestamps

Cheers,
Andrej

mongoose-timestamp adds 4 properties to collection when I customize the names

Hello,
I have the following in my code:

var mongoose = require('mongoose'),
      Schema = mongoose.Schema,
      timestamps = require('mongoose-timestamp');
var ItemSchema = new Schema({
      name: String
});
mongoose.plugin(timestamps,  {
    createdAt: 'added_at',
    updatedAt: 'last_updated'
});
ItemSchema.plugin(timestamps);

however when I look at my item collection using mongo command line I see that there is 4 properties (added_at, last_updated, createdAt and updatedAt)
what have I done wrong?
( @drudge ? )

Does not work with findOneAndUpdate and upsert

No created or lastUpdated properties are populated

can you override the dates? (to manually set them)

I have a situation where I am migrating some data and would like to preserve the modified dates from the original record. Can I manually set the created/modified dates and then have mongoose-timestamp skip its action so they are preserved?