@Ayende, That could be true, it is just in my case I need the current (most recently calculated) values :)
I think I will be able to work around this, just wanted to check here if this is something that could be considered a bug or not. Cheers Torkel On Jan 4, 4:20 pm, Ayende Rahien <[email protected]> wrote: > That actually sounds right, consider the fact that after a merge, you > usually execute BL, and you want to see the values as they were at the time > they were sent to you. > > On Mon, Jan 4, 2010 at 3:55 PM, Torkel Ödegaard > <[email protected]>wrote: > > > > > Hi, > > > I have an issue with the current way the Merge operations works when > > it comes to formula properties. > > > The merges operation uses the persister.GetPropertyValues(entity, > > source.EntityMode) to get the properties to copy over from the > > original to the target, this arrays of property values includes > > properties for formulas as well. This means that newly fetched and > > calculated forumula properties on the target entity will get > > overwritten by obsolete old calculated formula properties on the > > original entity. > > > Is this something that you have thought about? The Merge operation > > seems to copy all properties (except lazy ones), even update=false, > > insert=false properties. > > > I have been looking at a way to fix this, but there is not IsFormula > > property (or equivalent) on Property or StandardProperty class. > > > Should I create an issue for this in Jira?
