20.06 Mongoose

read the docs

npm install mongoose --save

Apparently there is an updateOne() method and also a replaceOne() method.

Mongoose TTL

IMPORTANT: MongoDB default stores dates UTC time zone.

const sessionTokenJsonSchema = {
    userId: {
        type: Schema.Types.ObjectId,
        required: true,
        description: "'userId' is required and must be a valid ObjectId",
    },
    expireAt: { type: Date, expires: 60, default: Date.now },
};
 
const sessionTokenSchema = new mongoose.Schema(sessionTokenJsonSchema);
const sessionTokens = mongoose.model('sessionToken', sessionTokenSchema);

The above example will have the sessionTokens created expire after 60 seconds. This means that the tokens will automatically be deleted by mongoDB without a server needing to clean it up.

here are more examples on how to set the { expires: 60}

// expire in 24 hours
schema.index({ prop1: 1 }, { expires: 60*60*24 })
 
// expire in 24 hours
schema.index({ prop1: 1 }, { expires: '24h' })
 
// expire in 1.5 hours
schema.index({ prop1: 1 }, { expires: '1.5h' })
 
// expire in 7 days
schema.index({ prop1: 1 }, { expires: '7d' })

When changing the time of the expiration date, it doesn’t auto update on the db side. So you’ll have to manually go to the “indexes” tab and delete the already existing TTL. The below example works the best for me,

const sessionTokenJsonSchema = {
    userId: {
        type: Schema.Types.ObjectId,
        required: true,
        description: "'userId' is required and must be a valid ObjectId",
    },
    deleted: {
        type: Date,
        default: Date.now,
        index: { expireAfterSeconds: 1 } // mongodb might have 1 minute delay, keep that in mind
    },
};

note that it doesn’t need to be a Date to use TTL, it just removes it after X time, after the value is set to a non-null value, and if you set it back to null in time, it won’t be deleted.