OK
I asked "why???" because I really didn't understand why.
I have another idea how to retrieve what we want and don't use OUTPUT
parameters.
What if to sql-insert add another attribute (list of properties). Example
(mapping by code):
m.SqlInsert("exec dbo.document_insert ?,?,?,?,?", new[] { t.CreateDate,
t.EditDate });
And at the end of "document_insert" write this:
SELECT SCOPE_IDENTITY, @CreateDate, @EditDate
I think it's elegant way of problem solving.
So, what will you say?
Понеділок, 22 квітня 2013 р. 22:08:42 UTC+3 користувач [email protected]
написав:
>
> I know nhibernate doesn't support output parameters? but I don't
> understand why.
> Why I can't write something like this:
>
> <class name="Document">
> ...
> <sql-insert>exec createDocument ?,? OUT,?,?</sql-insert>
> ...
> </class>
>
> I think it's very easy to implement.
>
> Now, for data access code I'm using pure ADO.NET. And my "documents"
> table has "CreateDate" column, which is set by server, and returns to my
> application by output parameter of stored procedure.
> I know I can set "CreateDate" property of my POCO class manually but i
> don't want do it because I can't accurately synchronize client clock to the
> clock of server.
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/nhusers?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
