[Mono-dev] The beta version of ADO.NET provider for MaxDB database
anagappan at novell.com
Mon Aug 7 05:43:28 EDT 2006
1. The preview version of ADO.NET will be available with Mono 1.2.
2. Can you please give more details regarding the SIGSEGV ? Procedures
to reproduce the bug ?
3. For running the general tests in Big Endian should be same as Little
Endian hardware. Recently lot of bugs related to Big Endian has been
fixed. So, there should not be any major concern. If you have any
issues, please let us know.
Dmitry Key wrote:
> I am currently working on an ADO.Net Provider for MaxDB that is registered
> in the SourceForge.net (see http://sourceforge.net/projects/maxdbprovider).
> The binaries are compiled for Net-1.1, Net-2.0 and Mono-1.0. Since the
> ADO.NET 2.0 is still in the development phase I can not build version for
> Mono-2.0. Provider is written in C# and can be compiled as fully managed
> assembly or managed wrapper for MaxDB client library. The former is more
> stable and portable the latter has better performance.
> I have the following question to the Mono developers:
> 1) When ADO.NET 2 implementation will be complete? Will it be included in
> the Mono 1.2?
> 2) I ran unit tests in the Debian Linux/Mono 1.1.13 and SUSE 9/Mono 1.1.16
> and the fully managed version was working less or more stable. But the
> unsafe provider failed dramatically with SIGSEGV signal. I checked program
> compiled by Mono 1.1.13 under .Net Framework 1.1 and everything worked fine.
> Thus the Mono P/Invoke mechanism is under suspicion. Could somebody give me
> some hint how to resolve this issue?
> 3) Could somebody help me to run test cases on the Big Endian hardware?
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Nagappan A <anagappan at novell.com>
Novell Software Development (I) Pvt. Ltd.
Linux Desktop Testing Project - http://ldtp.freedesktop.org
SUSE® Linux Enterprise 10
Your Linux is ready™
More information about the Mono-devel-list