                                                                                                                                                                                                                                                                
Received-SPF: temperror (google.com: error in processing during lookup of rich...@batemansr.us: DNS timeout) client-ip=209.85.223.174;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: [mongoose] No matching document found
From: Richard Bateman <rich...@batemansr.us>
In-Reply-To: <CACgri=sAdmFMBbhnYkjwb5rhov0Z7rN0=o0BQCcTK+3VcNd...@mail.gmail.com>
Date: Tue, 2 Oct 2012 14:34:14 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E78C5CD2-172A-435C-9817-64731C8E4...@batemansr.us>
References: <BF6450C0-FD66-4FB3-A1F9-E0D10C02C...@batemansr.us> <B243C207-B080-475E-917F-44442A92B...@gmail.com> <EAAE8DE1-23E0-4E14-AC33-708D4E85D...@batemansr.us> <CACgri=sAdmFMBbhnYkjwb5rhov0Z7rN0=o0BQCcTK+3VcNd...@mail.gmail.com>
To: mongoose-orm@googlegroups.com


I'll see if I can find time to throw something together.  The other =
issue turned out to be a document that was mistakenly saved twice in a =
row.

Does the version change *every* time the document is updated, or only =
when changes are made to an array?

Richard

On Oct 1, 2012, at 3:25 PM, Aaron Heckmann wrote:

> It would be nice to have code to test.
>=20
> "No matching document found" comes when attempting to make changes to
> an array by index position and the documents version already changed
> in the db. =
http://aaronheckmann.posterous.com/mongoose-v3-part-1-versioning
>=20
> You can disable versioning (not recommended) by setting your schema
> option: new Schema({..}, { versionKey: false })
>=20
> On Mon, Sep 24, 2012 at 1:38 PM, Richard Bateman =
<rich...@batemansr.us> wrote:
>>=20
>> Okay, I found one of the issues was caused by two saves called in the =
same request. The first only changes one field and it's not an array, =
the second changes an array.  Not sure why it should matter which occurs =
first since they dont' modify the same parts of the document; any =
thoughts? One is just updating a "last seen" timestamp and it's in our =
middleware and doesn't know about other modifications that might need to =
be made.
>>=20
>> Richard
>>=20
>> On Sep 13, 2012, at 3:30 PM, Aaron Heckmann wrote:
>>=20
>>> Odd indeed. Would you mind opening an issue with code to reproduce?
>>>=20
>>> https://github.com/LearnBoost/mongoose/issues/new
>>>=20
>>> On Sep 13, 2012, at 1:02 PM, Richard Bateman <rich...@batemansr.us> =
wrote:
>>>=20
>>>>=20
>>>> We recently updated to the 3.1.x branch and are using 3.1.2 from =
npm. I noticed recently that some of our models are now behaving a =
little oddly; every time I save after changing an array from our =
document I get the error "No matching document found". The weirdest =
thing, though, is that it still saves the document.
>>>>=20
>>>> Doing a little research it looks like this could be related to =
versioning, but nothing else is changing that document while I'm doing =
this (it's local on my dev box currently). Also the fact that it saves =
anyway but throws an error is really odd.
>>>>=20
>>>> Any ideas?
>>>>=20
>>>> Richard
>>>>=20
>>>> --
>>>> --
>>>> http://mongoosejs.com - docs
>>>> http://plugins.mongoosejs.com - plugins search
>>>> http://github.com/learnboost/mongoose - source code
>>>>=20
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Mongoose Node.JS ORM" group.
>>>> To post to this group, send email to mongoose-orm@googlegroups.com
>>>> To unsubscribe from this group, send email to
>>>> mongoose-orm+unsubscribe@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/mongoose-orm?hl=3Den
>>>>=20
>>>>=20
>>>=20
>>> --
>>> --
>>> http://mongoosejs.com - docs
>>> http://plugins.mongoosejs.com - plugins search
>>> http://github.com/learnboost/mongoose - source code
>>>=20
>>> You received this message because you are subscribed to the Google
>>> Groups "Mongoose Node.JS ORM" group.
>>> To post to this group, send email to mongoose-orm@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> mongoose-orm+unsubscribe@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/mongoose-orm?hl=3Den
>>>=20
>>>=20
>>=20
>> --
>> --
>> http://mongoosejs.com - docs
>> http://plugins.mongoosejs.com - plugins search
>> http://github.com/learnboost/mongoose - source code
>>=20
>> You received this message because you are subscribed to the Google
>> Groups "Mongoose Node.JS ORM" group.
>> To post to this group, send email to mongoose-orm@googlegroups.com
>> To unsubscribe from this group, send email to
>> mongoose-orm+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/mongoose-orm?hl=3Den
>>=20
>>=20
>=20
>=20
>=20
> --=20
> Aaron
> @aaronheckmann
>=20
> --=20
> --=20
> http://mongoosejs.com - docs
> http://plugins.mongoosejs.com - plugins search
> http://github.com/learnboost/mongoose - source code
>=20
> You received this message because you are subscribed to the Google
> Groups "Mongoose Node.JS ORM" group.
> To post to this group, send email to mongoose-orm@googlegroups.com
> To unsubscribe from this group, send email to
> mongoose-orm+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/mongoose-orm?hl=3Den
>=20
>=20