[Mono-list] ADO.NET plans for Mono 1.0
Sun, 20 Jun 2004 00:46:30 -0400
I updated the bug you mentioned...
Mono.Data.SybaseClient / Mono.Data.Tds works for me with:
Microsoft Windows XP Pro with SP1
Mono Beta 3 (Mono 0.96)
Sybase Adaptive Server Enterprise 12.5.1 (ASE or SQL Server)
They both work as Microsoft Visual Studio .NET 2002 (1.0) solution too.
I have a vs solution for these and the dependent projects if anyone is
interested. I had to define NET_1_0 for Mono.Security.dll to build
There are two things that are different:
- he is using Red Hat Linux 9 while I'm using Windows XP Pro SP1
- he is using Sybase 11.5 while I am using Sybase 12.5.1
Sybase has an ADO.NET data provider for Sybase ASE 12.5 and above, but
it seems like you have to be a paid customer to get it. They say their
ADO.NET provider will only work with Sybase ASE 12.0 and above. =20
I wonder if the character encoding between Sybase 11.5 and 12.5 is
different. Or maybe the encoding works differently between Windows XP
Pro SP1 and Red Hat Linux 9. Or maybe there is a i18n or l10n problem
[mailto:firstname.lastname@example.org] On Behalf Of S=E9bastien
Sent: Thursday, June 17, 2004 11:12 PM
To: Daniel Morgan; email@example.com
Subject: RE: [Mono-list] ADO.NET plans for Mono 1.0
> What problems are you having with Mono.Data.SybaseClient?
With SybaseClient, I cannot open a connection (exception thrown, see
I also tried the Generic Tds Provider. With this one, the connection
opens, but as soon as I execute a simple SQL request (SELECT) with the
datareader, the program hangs (I did not investigate why).
> 1. You could use our System.Data.OleDb or GDA# (found in GTK#) and=20
> libgda to connect to freetds. 2. An interesting alternative to try is=20
> use the jtds JDBC provider on IKVM running on Mono.
I will have a look at OleDb and GDA#.
The alternative #2 is not interesting for me, because it is actually an
argument "against" using mono for our project (The other option for the
project is to use Java).
As I said in my original message, we have to do a proof of concept that
will influence the choice of platform (mono vs Java). I would personnaly
prefer mono, but the risk must be acceptable... If the database access
is "shaky" for Sybase, we will undoubtedly choose Java.
The choice of Database is very important for us since all our actual
products use Sybase.
> I would look at freetds and jtds to see what's going on. Use my=20
> favorite debug tool Console.WriteLine().
Since I do not have any TDS background, I think that the learning curve
is too high for now and it would require too much of my time. I will
probably invest some time tracking bugs in the Odbc provider instead ...
Please let me know if there is any progress for the SybaseClient
Mono-list maillist - Monofirstname.lastname@example.org