Forces "_id" to be an instance of Mongo's ObjectId about laravel-mongodb

[jenssegers]

Is there an advantage in assigning your own values to the _id instead of a separate key? I don't really know any best practices about this.

[rms2219]

I'll tell you what I was trying to do; maybe I was doing something wrong.

I originally set my model to override the key using the field "email". What I was trying to do was, when I create and save a new instance of the model with the same key as an entry already in the database, I wanted Mongo to complain (like it does if I try to add an identical "_id"). When I override the key, it allows me to save as many new entries as I want, because it will create a new _id for each one.

Is there a way that I can use "email" as my key and have it throw an exception when I try to save a new model with the same key? If not, I see it as advantageous to be able to assign my own values to _id.

[hannesvdvreken]

@rms2219 is right. "_id" is indexed by default. Assign "_id" if you have a better primary key than the gibberish mongo_id.

[jenssegers]

@rms2219 check out the latest commit, it should fix your issue.

[rms2219]

@jenssegers Thanks for the quick fix!