I need to update an entity before it's saved, to modify it I need to use the documentsession and load another document and use it for calculating the value I need to change. When I do that I get an InvalidOperationException: Collection was modified; enumeration operation may not execute
On Wed, May 2, 2012 at 9:31 PM, marcus <mar...@meridium.se> wrote:
> I need to update an entity before it's saved, to modify it I need to use
> the documentsession and load another document and use it for calculating
> the value I need to change. When I do that I get an
> InvalidOperationException: Collection was modified; enumeration operation
> may not execute
On Wednesday, May 2, 2012, marcus wrote:
> I need to update an entity before it's saved, to modify it I need to use
> the documentsession and load another document and use it for calculating
> the value I need to change. When I do that I get an
> InvalidOperationException: Collection was modified; enumeration operation
> may not execute
Ok, I solved it by adding the stuff i needed to the parent. I think it will work ok
Den onsdagen den 2:e maj 2012 kl. 21:14:04 UTC+2 skrev Oren Eini:
> You can't modify the session while you are inside the store listenwr
> On Wednesday, May 2, 2012, marcus wrote:
>> I need to update an entity before it's saved, to modify it I need to use >> the documentsession and load another document and use it for calculating >> the value I need to change. When I do that I get an >> InvalidOperationException: Collection was modified; enumeration operation >> may not execute
> You can't modify the session while you are inside the store listenwr
> On Wednesday, May 2, 2012, marcus wrote:
>> I need to update an entity before it's saved, to modify it I need to use >> the documentsession and load another document and use it for calculating >> the value I need to change. When I do that I get an >> InvalidOperationException: Collection was modified; enumeration operation >> may not execute
I found this fact to be total crap when I was working with NHibernate and made NHibernate listeners entirely useless.
Why shouldn't you be able to load a document? I can understand not allowing MODIFYING loaded documents inside the listener but I certainly don't see why you can't get a copy of the document.
On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
> You can't modify the session while you are inside the store listenwr
> On Wednesday, May 2, 2012, marcus wrote:
>> I need to update an entity before it's saved, to modify it I need to use >> the documentsession and load another document and use it for calculating >> the value I need to change. When I do that I get an >> InvalidOperationException: Collection was modified; enumeration operation >> may not execute
On Wednesday, May 2, 2012 2:31:09 PM UTC-4, marcus wrote:
> I need to update an entity before it's saved, to modify it I need to use > the documentsession and load another document and use it for calculating > the value I need to change. When I do that I get an > InvalidOperationException: Collection was modified; enumeration operation > may not execute
My personal take: this will encourage people to do stuff that is considered
bad practice with RavenDB. If you want some other doc available to you, use
Includes when you first loaded the original document, why issue 2 different
commands? Or better - make sure to take this into account when modeling
On Wed, May 2, 2012 at 10:40 PM, Chris Marisic <ch...@marisic.com> wrote:
> I found this fact to be total crap when I was working with NHibernate and
> made NHibernate listeners entirely useless.
> Why shouldn't you be able to load a document? I can understand not
> allowing MODIFYING loaded documents inside the listener but I certainly
> don't see why you can't get a copy of the document.
> On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
>> You can't modify the session while you are inside the store listenwr
>> On Wednesday, May 2, 2012, marcus wrote:
>>> I need to update an entity before it's saved, to modify it I need to use
>>> the documentsession and load another document and use it for calculating
>>> the value I need to change. When I do that I get an
>>> InvalidOperationException: Collection was modified; enumeration operation
>>> may not execute
On Wednesday, 2 May 2012 20:40:26 UTC+1, Chris Marisic wrote:
> I found this fact to be total crap when I was working with NHibernate and > made NHibernate listeners entirely useless.
> Why shouldn't you be able to load a document? I can understand not > allowing MODIFYING loaded documents inside the listener but I certainly > don't see why you can't get a copy of the document.
But for this to work wouldn't you have to ask the session to load a doc, but not track/cache it, otherwise it's always possible for it to be changed?
I guess you could use the low-level Advanced API's like you said in your other reply. Or if there was some way of saying to the session, that you want to load a doc, but don't track it, but I guess that's what the low-level API is for.
> On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
>> You can't modify the session while you are inside the store listenwr
>> On Wednesday, May 2, 2012, marcus wrote:
>>> I need to update an entity before it's saved, to modify it I need to use >>> the documentsession and load another document and use it for calculating >>> the value I need to change. When I do that I get an >>> InvalidOperationException: Collection was modified; enumeration operation >>> may not execute
I fixed this so this wouldn't throw, but it still had a lot of bad
implications.
For example, the newly loaded entity will not be part of the current Unit
of Work, so changes made to it won't be captured.
On Wed, May 2, 2012 at 10:40 PM, Chris Marisic <ch...@marisic.com> wrote:
> I found this fact to be total crap when I was working with NHibernate and
> made NHibernate listeners entirely useless.
> Why shouldn't you be able to load a document? I can understand not
> allowing MODIFYING loaded documents inside the listener but I certainly
> don't see why you can't get a copy of the document.
> On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
>> You can't modify the session while you are inside the store listenwr
>> On Wednesday, May 2, 2012, marcus wrote:
>>> I need to update an entity before it's saved, to modify it I need to use
>>> the documentsession and load another document and use it for calculating
>>> the value I need to change. When I do that I get an
>>> InvalidOperationException: Collection was modified; enumeration operation
>>> may not execute
The most primary use case for needing to load a document from the DB would be to load User Document so you could insert denormalized data into the document you're saving.
On every system action I save the userid & username (denormalized, don't really care if they change it later it makes it easier for a human to understand if they look at history and see b...@site.com and not just userid:234347). I created a custom authentication system that exists outside of raven and allows me access to my full user object at all times, without having that functionality I could very well want to load a user document instead. (This was what I wanted to do in nhibernate but couldn't, and is part of the reason I built my auth system as I did, and by build i mean build on top of forms auth not roll my own entire security system)
Also I could see the use case similar to the OPs when working with hierarchical data that a change to a child object could theoretically need to change the parent object.
On Thursday, May 3, 2012 5:22:53 AM UTC-4, Oren Eini wrote:
> I fixed this so this wouldn't throw, but it still had a lot of bad > implications. > For example, the newly loaded entity will not be part of the current Unit > of Work, so changes made to it won't be captured.
> On Wed, May 2, 2012 at 10:40 PM, Chris Marisic <ch...@marisic.com> wrote:
>> I found this fact to be total crap when I was working with NHibernate and >> made NHibernate listeners entirely useless.
>> Why shouldn't you be able to load a document? I can understand not >> allowing MODIFYING loaded documents inside the listener but I certainly >> don't see why you can't get a copy of the document.
>> On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
>>> You can't modify the session while you are inside the store listenwr
>>> On Wednesday, May 2, 2012, marcus wrote:
>>>> I need to update an entity before it's saved, to modify it I need to >>>> use the documentsession and load another document and use it for >>>> calculating the value I need to change. When I do that I get an >>>> InvalidOperationException: Collection was modified; enumeration operation >>>> may not execute
Chris, for both scenarios mentioned I can see an easier way out -
For storing user data, just have that user entity handy by using Includes
or saving the current user object in the HTTP session context
For hierarchical data, if changes made to a child document always affect
the parent, you might want to store a large document to hold the hierarchy
details instead of doing this within the entities themselves. Doing this,
especially if that is a common operation, violates the transactional
boundary
On Thu, May 3, 2012 at 3:53 PM, Chris Marisic <ch...@marisic.com> wrote:
> The most primary use case for needing to load a document from the DB would
> be to load User Document so you could insert denormalized data into the
> document you're saving.
> On every system action I save the userid & username (denormalized, don't
> really care if they change it later it makes it easier for a human to
> understand if they look at history and see b...@site.com and not just
> userid:234347). I created a custom authentication system that exists
> outside of raven and allows me access to my full user object at all times,
> without having that functionality I could very well want to load a user
> document instead. (This was what I wanted to do in nhibernate but couldn't,
> and is part of the reason I built my auth system as I did, and by build i
> mean build on top of forms auth not roll my own entire security system)
> Also I could see the use case similar to the OPs when working with
> hierarchical data that a change to a child object could theoretically need
> to change the parent object.
> On Thursday, May 3, 2012 5:22:53 AM UTC-4, Oren Eini wrote:
>> I fixed this so this wouldn't throw, but it still had a lot of bad
>> implications.
>> For example, the newly loaded entity will not be part of the current Unit
>> of Work, so changes made to it won't be captured.
>> On Wed, May 2, 2012 at 10:40 PM, Chris Marisic <ch...@marisic.com> wrote:
>>> I found this fact to be total crap when I was working with NHibernate
>>> and made NHibernate listeners entirely useless.
>>> Why shouldn't you be able to load a document? I can understand not
>>> allowing MODIFYING loaded documents inside the listener but I certainly
>>> don't see why you can't get a copy of the document.
>>> On Wednesday, May 2, 2012 3:14:04 PM UTC-4, Oren Eini wrote:
>>>> You can't modify the session while you are inside the store listenwr
>>>> On Wednesday, May 2, 2012, marcus wrote:
>>>>> I need to update an entity before it's saved, to modify it I need to
>>>>> use the documentsession and load another document and use it for
>>>>> calculating the value I need to change. When I do that I get an
>>>>> InvalidOperationException: Collection was modified; enumeration operation
>>>>> may not execute
