.. hm..

my question in the subject.... ))

No, NH-139 is the JIRA issue for it, in case you want to track it.

This is very ruefully :((

I have a very complicated logic in a stored procedure. Maybe there is some way that allows me to use it in NHibernate? Or I need to wait?

You can obtain an IDbConnection object from the NHibernate session, and execute any commands using this. The following code assumes that the session object is an open NH session, and runs stored procedure MyStoredProc.

What you can't currently do is run a stored procedure that returns data and map the data to persistent objects.

You also need to be aware that if your stored procedure amends the data in your tables, this will not be reflected in any persistent objects already loaded.

Finally, you should consider moving (as much as possible) your logic from stored procs to your entities :wink:

That is bad, because the procedure returns data...and I need it.

How I understand, there is no the way at this moment in NHibernate to load data from stored procedure to persistent objects :(

2KPixel

This is mpossible or is very difficult...

Regarding using stored procedures:

1) For saving (inserting/updating/deleting): Because a class can define its own persistence strategy (by using its own IClassPersister implementation and using the attribute "persister" in the mapping file), it is possible to redirect the insert/update/delete operations to call stored procedures, instead of generating dynamic SQL.

In this case, the basic strategy would be:

o Inherit from the appropriate IClassPersister class (AbstractEntityPersister, EntitiyPersister or NormalizedEntityPersister)

o Override the corresponding Generate[Insert | Update | Delete]Strings method, to build a stored procedure call, instead of a DML SQL string.

o Override the corresponding action method(s) (Insert(), Delete(), Update()).

2) For loading data: I guess that if you are using a RDMBS that supports user-defined functions that return result sets, the best strategy is to:

o Move the logic from the stored procedure to a user-defined function
o Create a view that returns the result set from the user-defined function
o Use the columns of the view in the Xml mapping file
o Of course, to persist such class, you will need to define you own IClassPersister, as explained in the item 1.

I have tested item 1 with my object model and worked fine. Item 2 still needs to be tested.