https://bugzilla.novell.com/show_bug.cgi?id=437312


           Summary: System.Data.Odbc and Mono 2.0 : Many new problems
                    upgrading from 1.9.1
           Product: Mono: Runtime
           Version: 2.0
          Platform: Other
        OS/Version: RHEL 4
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [email protected]
          Found By: Third Party Developer/Partner


We have found many things which work in version 1.9.1, and work in MS.NET, but
which have stopped working in version 2.0.

The release notes say nothing about odbc changes, though the subversion logs
show many changes between these two releases.

To give one example:

I have a problem e.g. with the constructor public OdbcParameter(string
name,Object value) with a string parameter.
It worked before (1.9.1) like this, and still does in Microsoft .net 2.0:
        parameters[0] = new OdbcParameter("partnershortname",
(System.Object)"Pok%"); 

But now with mono 2.0 we get this exception:
System.Data.Odbc.OdbcException: ERROR [22001] [DataDirect][ODBC PROGRESS
driver]String data, right truncated.  Error in parameter 1.
The workaround is:
       parameters[0] = new OdbcParameter("partnershortname", OdbcType.VarChar,
20);
       parameters[0].Value = (System.Object)"Pok%";


We also notice that this user is having odbc difficulties since 2.0 was
released:

http://go-mono.com/forums/#nabble-tc19884966

As and when we have time we will file separate bugs for the other odbc issues
we are finding but we wanted to give you early notice of these problems.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to