None in this world worked with Nhibernate and oracle stored procedure before?

15.3. Custom SQL for create, update and delete.

15.3. Custom SQL for create, update and delete The order of the positional parameters is currently vital, as they must be in the same sequence as N You can see the expected order by enabling debug logging for the NPersister. Entity level. With this level enabled Nbernate will print out the static SQL that is used to create, update, delete etc. Entities.

(To see the expected sequence, remember to not include your custom SQL in the mapping files as that will override the Nbernate generated static sql.) I'd guess it's in the same order as the properties are mapped?

You could so something like this. Session. CreateSQLQuery("call strored_proc(:a, :b, :c, :d)") .

SetInt64("a", 54) . SetInt64("b", 544) . SetString("c", "your value") .

SetInt64("d", 6546546) .ExecuteUpdate(); Where a,b,c,d are parameters to your function. Call .List() on it for it to return a 2 dimensional object array. If want want to do a mapping: call strored_proc(:a, :b, :c, :d) Then in your C# code session.

GetNamedQuery("StoredProcName") . SetInt64("a", 54) . SetInt64("b", 544) .

SetString("c", "your value") . SetInt64("d", 6546546) .ExecuteUpdate(); or again call .List(); if you need results instead of .ExecuteUpdate().

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.