That's handy to know, cos I've got Oracle locally. Cheers Frans.
--------------------------------------------------
From: "Frans Bouma" <[email protected]>
Sent: Tuesday, July 27, 2010 1:37 PM
To: <[email protected]>
Subject: RE: [nhibernate-development] NH-1981 and databases without named
parameters
Not exactly.
Looking a little deeper, it's the ODBC driver (or ODBC in general) that
doesn't support named parameters.
DB2's ADO.NET provider and Sybase ASA's ADO.NET provider also don't
support named parameters, so for these databases the problem exists as
well.
So out only option might be to revert to using the parameters in order
(and
not being able to support http://216.121.112.228/browse/NH-1981
<http://216.121.112.228/browse/NH-1981> ).
Alternatively, we could maybe expand the parameter lists for drivers that
don't support it? I'm not sure which is more work at this point.
I'm not sure if NHibernate internally anonymizes the parameters
after the query has been generated internally. If so, one could solve it
in
that 'anonymizer', otherwise it might indeed be a bit cumbersome.
I do recall, but am not 100% sure, that multiple usage of the same
parameter causes problems in ODP.NET as well, so a test for that is
perhaps
necessary on that particular ado.net provider.
FB
From: Fabio Maulo <mailto:[email protected]>
Sent: Tuesday, July 27, 2010 12:54 PM
To: [email protected]
Subject: Re: [nhibernate-development] NH-1981 and databases without
named parameters
On Mon, Jul 26, 2010 at 7:42 PM, Richard Brown
<[email protected]> wrote:
Ah, I see you said it doesn't support named parameters.
Crap. Rethink required. :-(
Sent from my Android phone.
An issue to the Informix DataProvider is not appropriate ?
--
Fabio Maulo
