Fork me on GitHub


Q. Why don't my changes to arrays get saved when I update an element directly?

doc.array[3] = 'changed';;

A. Mongoose doesn't create getters/setters for array indexes; without them mongoose never gets notified of the change and so doesn't know to persist the new value. The work-around is to first mark the path of the array modified before saving.


Q. Why doesn't mongoose allow me to directly assign schemas to paths?

var userSchema = new Schema({ name: String });
new Schema({ user: userSchema })

A. Schemas have a one-to-one mapping with documents. Documents have save and remove methods along with their own pre and post hooks which would lead to code like the following:;  // ?
doc.user.remove();// ?

We've felt that this api would be more confusing than helpful. The counter argument is that arrays of sub-documents already have this functionality, but at best this too leads to confusion (calling save on a sub-document is a no-op and exists only to support pre save hooks). In the future this is likely to be revisited.

Q. How can I enable debugging?

A. Set the debug option to true:

mongoose.set('debug', true)

Q. My save() callback never executes. What am I doing wrong?

A. All collection actions (insert, remove, queries, etc) are queued until the connection opens. It is likely that an error occurred while attempting to connect. Try adding an error handler to your connection.

// if connecting on the default mongoose connection
mongoose.connection.on('error', handleError);

// if connecting on a separate connection
var conn = mongoose.createConnection(..);
conn.on('error', handleError);

Something to add?

If you'd like to contribute to this page, please visit it on github and use the Edit button to send a pull request.