session.IsDirty() partially flushes

Chuck111 · **Joined:** Tue Dec 18, 2007 7:22 am **Posts:** 4

Hi,

calling session.IsDirty() executes inserts for new rows in a set mapped with inverse="true" even with FlushMode.Never

Obviously a bug?

Not only it prevents using this method for change tracking but it also prevents unique constraints on collection items e.g. if you load the container, delete an item and add similar one again, unique constraint fails, since dirty check in commit executes inserts before old row is deleted.

--Chuck

Chuck111 · **Joined:** Tue Dec 18, 2007 7:22 am **Posts:** 4

Problem seems be that my collection items are mapped with id generator="identity" and collection cascade="all".

Why does the dirty check force an id assign? As I see it, if it finds a transient instance in a cascading collection, it should stop dirty checking and return true immediately.

Is there a workaround for this?

--Chuck

whoami · **Joined:** Mon Aug 29, 2005 3:07 pm **Posts:** 77

What version of NHibernate are you using ?

If it is indeed a bug (imho it is unexpected behaviour, so , imho it is a bug), I would file a bug-report on NHibernate's issue-tracker[/url]

Chuck111 · **Joined:** Tue Dec 18, 2007 7:22 am **Posts:** 4

Tested with 1.2.1 and 2.0 RC1. Same behaviour with both.

Maybe I will file a report since this is pretty easy to produce.

--Chuck

haugern · **Joined:** Wed Apr 02, 2008 3:09 pm **Posts:** 2

I experience the same problem. Have you found a solution?