X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fado-net;h=cd6ea65cfe42786a88044795167c06f4ab24123f;hb=c399f703115667c1746c052b5e4a393ce182c5dc;hp=0f40c246db850c254411499bef27532627d6a796;hpb=c40860f8f6073bf2e89beb08857b7e5b1cfb39bc;p=mono.git diff --git a/web/ado-net b/web/ado-net index 0f40c246db8..cd6ea65cfe4 100644 --- a/web/ado-net +++ b/web/ado-net @@ -1,96 +1,235 @@ * ADO.NET -

Mono's ADO.NET Developers: -

+

Mono's ADO.NET Developers: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DeveloperEmailContribution
Rodrigo Moyarodrigo -AT-
ximian.comNOSPAM		ADO.NET coordinator,
OLE DB provider,
and tests
Daniel Morgandanmorg -AT-
sc.rr.comNOSPAM		MySQL, PostgreSQL,
Oracle providers,
and tests
Tim Colemantim -AT-
timcoleman.comNOSPAM		Microsoft SQL Server,
Sybase,
TDS providers,
Oracle, +
and tests.
+ He has + contributed
to other parts
of Mono too,
such as, +
EnterpriseServices, + XML,
and WebServices.
Brian Ritchiebrianlritchie -AT-
hotmail.comNOSPAM		ODBC provider
and the ProviderFactory
in Mono.Data
Vladimir Vukicevicvladimir -AT-
pobox.comNOSPAM		SQL Lite provider.
He has contributed to GTK#
and mPhoto too.
Christopher Bocknercleared -AT-
rogers.comNOSPAM		IBM DB2 Universal
Database provider
Ville Palovi64pa -AT-
koti.soon.fiNOSPAM		XML stuff
in System.Data
including DataSet
+ and XmlDataDocument,
and tests
Gonzalo Paniagua Javiergonzalo -AT-
ximian.comNOSPAM		Integration between
System.Web and
System.Data
Gaurav Vaishgvaish -AT-
iitk.ac.inNOSPAM		Web controls
Phillip JerkinsPhillip.Jerkins -AT-
morgankeegan.comNOSPAM		Named Instance support
in System.Data.SqlClient
+ +** Bugs and Feature Requests + +

+ +** ADO.NET Data Providers -* Action plan +

List of ADO.NET Data Providers working in Mono: + +

-

The current plan to implement ADO.NET is as follows: +

Providers which we do not have, but we would like to have. Currently, + some of these databases are supported via the ODBC or OLE DB providers. -

+ +** Extra Classes in Mono ADO.NET + +

An ADO.NET Provider Factory + was created by Brian Ritchie. The + Provider Factory is a way to dynamically create + connections, commands, parameters, and data adapters based on configuration + information. -* Current Status +** Current Status -

Variouls ADO.NET Providers have been created: PostgreSQL, MySQL, Sybase, SQL Lite, - Microsoft SQL Server, OLE DB, ODBC, and TDS Generic. See their respective web page for - more information. +

Various ADO.NET Providers have been created at various stages of + development including: + Firebird/Interbase, IBM DB2 Universal Database, MySQL, ODBC, OLE DB, Oracle, + PostgreSQL, SQL Lite, Sybase, Microsoft SQL Server, and TDS Generic. + See their respective web page for more information. + +

Data Relations via DataRelation, DataRelationCollection, and + other classes have not been implemented + +

Constraints need lots of work -

Constraints need lots of work +

XML Schema Definition tool xsd.exe that is included + in the .NET Framework has not been created for Mono -

TypeDataSetGenerator needs to be stubbed and implemented. +

TypeDataSetGenerator needs to be stubbed and implemented.

DataSet, DataAdaptor, DataTable, DataRelation, DataRow, DataColumn, DataColumnCollection, DataRowCollection, and others need more work. There are - many classes that are just stubs and need to be implemented. + many classes that are just stubs and need to be implemented. Ville Palo has been + doing much testing here.

XML support in System.Data needs work. This involves working on the classes: DataSet, XmlDataDocument, and the method ExecuteXmlReader() that @@ -123,22 +279,13 @@ Stuart Caborn has started the XML support in a DataSet. Tim Coleman started XML support in the ExecuteXmlReader() in a SqlCommand. Ville Palo has been heavily modifying DataSet, XmlDataDocument, and other classes for reading - and writing XML. - -

ADO.NET Provider Factory has been started by Brian Ritchie. The - Provider Factory is way to dynamically create - connections, commands, parameters, and data adapters based on configuration information. The - provider factory also provides utility functions needed by a lot of - providers but are not exposed via the provider. The ProviderFactory - is found at mcs/class/Mono.Data and includes a test named test.cs for it in - mcs/class/Mono.Data/Test. Also, take a look at the sample .config file for the - test.exe application named test.exe.config. The .config file is automatically - read when you use the Mono.Data.ProviderFactory or Mono.Data.DataTools. + and writing XML. XML Serialization support in DataSet needs to be implemented. -

Integration with ASP.NET has not been started, such as, data binding - to a System.Web.UI.WebControls.DataGrid. This may involve implementing many classes - in System.Web and System.Data. If you want to help, - contact Gonzalo Paniagua Javier. Here is information about using ADO.NET in ASP.NET: +

Integration with ASP.NET has been created. Data binding of + a DataTable in a DataSet to a System.Web.UI.WebControls.DataGrid works. Data binding + of other types works too. + +

Database Access from ASP.NET:

-* Testing +** Testing +