The fix on stackoverflow removes the default behavior, which is not
recommended. This is the from the NHibernate source.
/// <remarks>
/// This adds logic to ensure that a DbType.Boolean parameter
is not
created since
/// ODP.NET doesn't support it.
/// </remarks>
protected override void InitializeParameter(IDbDataParameter
dbParam, string name, SqlType sqlType)
{
// if the parameter coming in contains a boolean then
we need to
convert it
// to another type since ODP.NET doesn't support
DbType.Boolean
switch (sqlType.DbType)
{
case DbType.Boolean:
base.InitializeParameter(dbParam, name,
SqlTypeFactory.Int16);
break;
case DbType.Guid:
base.InitializeParameter(dbParam, name,
GuidSqlType);
break;
default:
base.InitializeParameter(dbParam, name,
sqlType);
break;
}
}
On 30 Aug., 14:45, Dries Verbeke <[email protected]> wrote:
> Check out this
> post<http://stackoverflow.com/questions/7684163/problems-with-nhibernate-a...>for
> the answer
>
>
>
>
>
>
>
> On Friday, August 17, 2012 5:15:54 AM UTC+2, Milind wrote:
>
> > did you found the solution as I have similar issue.
>
> > please let me know
--
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.
