1.2 Beta 2 against SQL Server 2005

I can't seem to get the <sql-insert> override to work for me. sql-delete and sql-update work fine but no matter what I do the insert tries to use its own INSERT statement instead.

am I doing something wrong?

here is my very simple mapping:

<class name="DocumentData" table="Document" lazy="false">
<id name="ID" type="long">
<generator class="native" />
</id>
<property name="Comment" type="String" />
<sql-insert>exec SetDocument ?, ?</sql-insert>
<sql-update>exec SetDocument ?, ?</sql-update>
<sql-delete>exec DeactivateDocument ?</sql-delete>
</class>


I am using the table reference in the class so that I get an automatic SELECT statement built for me, but I want to handle the filing myself. I tried removing the table reference and using a custom loader but then it tried to use an INSERT statment against the class name instead of the table name.

is it the fact that I have an "id" defined for the table? should I just make that a regular "property" instead?

any advice is most appreciated

sql-insert doesn't work with native generators. Change to a different identifier generation strategy.

thanks Sergey.

changing the generator type definitely made it start using the stored procedure for inserts, but now I have a new problem...

I have an existing database, and as part of that the same stored procedures are being used for both inserts and updates (as you can see in my mapping). in my current application I am generating the ID field for the object/row within the stored procedure and returning that as either an output parameter or return value - so for an insert I would provide an ID = 0 and the procedure would know to do an insert and generate the ID for me, for an update I would just pass in the actual ID of the row and the procedure knows to do an update instead.

so what I would like NHibernate to do in this case is to use the stored procedure for the insert, and ALSO be able to automatically populate the ID in the object subsequent to that procedure call. this doesn't seem possible without some kind of output parameter/return value coming from the procedure and some way of telling NHibernate to look at it.

have a run into a show stopper (assuming I can't change the way my database/procedures currently work)?

NHibernate does not currently support returning identifiers from stored procedures or using them to generate an identifier, unfortunately.

thanks again Sergey. I recognize that what I am doing is not necessarily a mainstream case... I guess I am trying too many "tricks" at once :-)

Hi mcole_ge and sergey,

can you pls. let me know which generator class you are using to make it work?

Many thanks

I think I used "assigned"