I think that a cleaner solution would be a separate project, but that would
work as well.
Can you create a patch for those?
On Sun, Sep 28, 2008 at 1:15 PM, Artur Dorochowicz <
[EMAIL PROTECTED]> wrote:
>
> OK, I get it now.
>
> I just thought about this solution below. It would save us from
> creating a new project.
>
> using System.Reflection;
> ...
>
> protected override void InitializeParameter(IDbDataParameter dbParam,
> string name, SqlType sqlType)
> {
> base.InitializeParameter( dbParam, name, sqlType );
>
> if( sqlType is BinarySqlType )
> {
> PropertyInfo property =
> dbParam.GetType().GetProperty( "SqlDbType" );
> property.SetValue( dbParam, SqlDbType.Image, null );
> }
> else if( sqlType is StringSqlType )
> {
> PropertyInfo property =
> dbParam.GetType().GetProperty("SqlDbType");
> property.SetValue( dbParam, SqlDbType.NText, null );
> }
> }
>
> PropertyInfo creation could of course be moved outside and done once
> for the lifetime of the driver.
>
> If that's not acceptable then how do I go about contributing to
> NHContrib project?
>
>
> On 27 Wrz, 21:56, "Ayende Rahien" <[EMAIL PROTECTED]> wrote:
> > The issue is that for most drivers, length really doesn't matter for the
> > type you are using. Those are orthogonal concepts.The problem with the
> > scenario you outline is that for SQL CE, it _still_ doesn't matter, but
> you
> > have to set a SQL CE value as the param type to get it to work.
> > That is why I think that taking your code and spinning it into a full
> driver
> > project would be the best thing. That driver project could take a
> dependency
> > on the SQL CE assembly and use it
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
