I Upgraded from NHibenate 1.2 CR1 to 1.2 GA.
i'm using nhbibernate for mapping legacy things.
that's why i've to use assigned keys for some tables :-(
i'm using SAVE and Update as suggested,
so seems ok to me.

Since 1.2GA my nunit-tests fail when i create new entitys and attach
additional data to these entrys in the same session.

Things worked fine in 1.2 CR1 and all versions before since (0.8.0)
i think nhibernate trys to persist my data twice now.
Now i get 'Unexpected row count: 2; expected: 1' exception during commit...

Maybe there's a need now, to save bofore attaching aditional data ?

But i also might be a general trouble with asigned keys now, that's why i want to know if i'm doing something wrong.
(i also removed unsaved-value="null" which i had before in key-mapping, but didn't solve anything)

Would be great to hear any new ideas...

i tryed to 'reduce the problem as far as possible'

greetings
helmut

Hibernate version:
1.2.GA
Mapping documents:


Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:
mssql2005 in 2000 compatibility mode
The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:


Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html[/code]

Not sure if your problem is the same as mine but I am tinkering with NHibernate and just got this message myself. The problem I have is that my table has various triggers listening for inserts and updates. Any rows affected by a trigger gets added to the row count returned back to NHibernate.

To verify this, just run the SQL emitted by NHibernate, in my case I have:

(0 row(s) affected)

(3 row(s) affected)

(1 row(s) affected)

(1 row(s) affected)


What I've seen people suggest is to alter the trigger as such:

SET NOCOUNT ON
-- Trigger actions
SET NOCOUNT OFF

My question to the community is: What if this is not an option? I have a legacy database that can't easily be adapted to fit NHibernate's wishes. I'll probably start browsing the NHibernate source code after this, but can we have an option to turn off this row count check (as inadvisable as that may be)?

Thanks

DRapp,
you made my week :-))

AARGHHH.
YESSS.. there is a trigger watching on this table,
which insert's a row in another table on inserts.

I think i would never have found out for myself,
that this is the reason of getting duplicate row count...
will have a try on 'SET NOCOUNT ON' as you suggested, now...

Thanks
Thanks
Thanks :-))))

Helmut