@Fabio I didn't mean output parameters. OUTPUT statement can return the whole row. It would also be handy if you are using optimistic locking with timestamp fields.
Tapio On Nov 7, 8:33 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > That is one of the next feature of NH2.1.It is identity using return > parameter instead select statement. > The feature will be available for various dialects including ORACLE (in > Oracle is a sequence generated by a trigger). > > The feature will be active setting the property > adonet.use_get_generated_keys="true" for "identity" generator. > > BTW is better if you avoid it and avoid identity or identity-like > generators. > > Bye. > Fabio Maulo > > 2008/11/7 Tapio Kulmala <[EMAIL PROTECTED]> > > > > > @Ayende > > > Are you familiar with the T-SQL 2005 OUTPUT statement? It could help > > if we want to avoid extra roundtrips to the DB. > > > For example, try this > > > DECLARE @Test TABLE > > ( TestId [int] IDENTITY(1,1) NOT NULL > > , Amount decimal(10,2) > > , ts timestamp ) > > > INSERT INTO @Test (Amount) > > OUTPUT INSERTED.* > > VALUES (100) > > > UPDATE @Test SET Amount = Amount * 10 > > OUTPUT INSERTED.* > > WHERE TestId = 1 > > > Could sql2005 dialect take advantage of this feature? > > > Tapio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
