Apparently even if a lot of NH expert continue saying that "identity" is absolutely not the best strategy as ID generetor the NH-MSSQL community continue to no hear.Customs SQL are not designed to work with Post-Insert-Identifier-Generator; in the future, probably, we can do something for some Post-Insert-Identifier-Generator but I don't think it is possible do it for Identity. If somebody discover a flex solution a patch is welcome.
2008/9/29 James Nail <[EMAIL PROTECTED]> > > Hi guys, > I just ran into the issue described in this jira item: > http://jira.nhibernate.org/browse/NH-727, > Where custom sql-insert (via stored proc or direct SQL) statements > defined in mappings will throw an exception ("Parameterized Query > '(@p0 int,@p1 nvarchar(7),@p2 int)exec InsertTest @p0, @p1' expects > parameter @p2, which was not supplied.") if SQL server identity is > used for primary keys. > > Anyone have any ideas about this issue or its possible workarounds? > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
