Frans,
Reflection is fine; the idea is not to eliminate reflection, but to ease
deployment.
Diego
On Fri, Aug 13, 2010 at 18:54, Frans Bouma <fr...@sd.nl> wrote:
> > I see... I didn't know that.
> > However, there's a problem with that solution: I lose version
> independency.
> > That problem is fixed by the DbProviderDriver without introducing any
> > problems that I can think of.
>
> DbProviderFactory has some problems with ODP.NET: if you want to
> have named parameters, you have to set the BindByName property on the
> OracleConnection. This is a property on the class provider by ODP.NET, not
> in DbConnection. I've to check, but if memory serves me correctly, there's
> also a problem with Sybase ASA.
>
> So in short, even if you use DbProviderFactory, you need some
> reflection to use it.
>
> FB
>
> >
> > Diego
> >
> >
> >
> > On Fri, Aug 13, 2010 at 14:23, Fabio Maulo <fabioma...@gmail.com> wrote:
> >
> >
> > You don't have to.
> > In our tests you can see how redirect a partial assembly-name.
> >
> >
> > On Fri, Aug 13, 2010 at 12:15 PM, Diego Mijelshon
> > <di...@mijelshon.com.ar> wrote:
> >
> >
> > This is a great patch, we currently have to copy
> > IBM.Data.Informix.dll everywhere.
> >
> >
> > I can create the DPF-based Informix driver if this gets
> > included.
> >
> > Diego
> >
> >
> >
> > On Fri, Aug 13, 2010 at 11:41, Pablo Ruiz
> > <pablo.r...@gmail.com> wrote:
> >
> >
> > Hi,
> >
> > By reading the details at
> > http://216.121.112.228/browse/NH-1378 looks like this was an old request
> > (1.2.1 days) which has been considered already. How ever (surelly due to
> > time constraints ;)) this is still an open issue, which may be considered
> > now for NH3.
> >
> > I have a couple of classes implementing a base
> driver
> > using DbProviderFactory, and I have attached them to the jira issue, so
> > anyone can review them... This one are copied from my own project, but
> they
> > are simple enought to get an starting point from which a discussion can
> be
> > started.
> >
> > The point behind this issue (for me) it's mainly
> mono
> > compatibility, as mono does not implement 'BindingRedirect' support, and
> as
> > such, the only way of making NH work it's by placing the ado.net
> provider's
> > assembly at bin folder, which in some deployments it's far from perfect.
> >
> > As such, if having alternate driver implementations
> > using Reflection (current one) and DbProviderFactory (the alternate one)
> > looks great for Fabio & co, I can provide fully-functional patches
> against
> > trunk, just letme know about it.. ;)
> >
> > Saludos.
> > Att. Pablo
> >
> >
> >
> >
> >
> >
> > --
> > Fabio Maulo
> >
> >
> >
>
>
>
