Support for ADO.Net Provider?


Author
Message
Ben Hayat
Ben Hayat
Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)
Group: Forum Members
Posts: 374, Visits: 1.2K
Most new third party database vendors offer "ADO.Net Provider" instead of OLD DB. Is there any plan to support this newer technology out of the box? Or perhaps have native support for MySQL?



Thanks!

..ßen
Gary C Wynne
Gary C Wynne
StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)StrataFrame Beginner (30 reputation)
Group: Forum Members
Posts: 26, Visits: 236

>Most new third party database vendors offer "ADO.Net Provider" instead of OLD DB.

The provision of a specific ADO.Net Provider is down to the database vendor or, third party vendors. In .NET, out of the box, you get a SQL Server and Oracle ADO.Net Provider(s). Take a look at this link http://msdn2.microsoft.com/en-us/library/system.data.common.dbproviderfactory_members.aspx - this will tell you about the DBProviderFactory members. Basically, if you create this factory, you can access a set of methods that give access to a specific providers implementation of the datasource classes.

>Is there any plan to support this newer technology out of the box? Or perhaps have native support for MySQL?

See http://www.crlab.com/mysqlnet/ - this company provide a MySQL ADO.Net data provider.


Ben Hayat
Ben Hayat
Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)Advanced StrataFrame User (572 reputation)
Group: Forum Members
Posts: 374, Visits: 1.2K
Gary C Wynne (01/13/2007)




>Most new third party database vendors offer "ADO.Net Provider" instead of OLD DB.



The provision of a specific ADO.Net Provider is down to the database vendor or, third party vendors. In .NET, out of the box, you get a SQL Server and Oracle ADO.Net Provider(s). Take a look at this link http://msdn2.microsoft.com/en-us/library/system.data.common.dbproviderfactory_members.aspx- this will tell you about the DBProviderFactory members. Basically, if you create this factory, you can access a set of methods that give access to a specific providers implementation of the datasource classes.



>Is there any plan to support this newer technology out of the box? Or perhaps have native support for MySQL?



See http://www.crlab.com/mysqlnet/- this company provide a MySQL ADO.Net data provider.







Gary, I think you missread my post. I know Corelab offers ADO.Net Provider, and so as many other database vendors. My question from SF team is that if they will add support for ADO.net provider in SF, so we can use other database via ADO.net provider rather than OLEDB, which is more recent to .Net development.



However, with the advent of LINQ and the new interface, ADO.Net provider will be changed anyway!

..ßen
StrataFrame Team
S
StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)StrataFrame Developer (4.6K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
Yes, you can use any ADO.NET provider you like... MySql, Advantage, DB2, VistaDB... they all have a native ADO.NET provider.  However, you will need to create a specific DbDataSourceItem implementation for that provider.  The DbDataSourceItem is used within SF to create the dynamic SQL Statments that process the INSERTS, UPDATES, and DELETES.  So, you can create a new DbDataSourceItem using the SqlDataSourceItem as your template and replace the SqlCommand objects and so forth with your MySqlCommand objects.  Other things will need to change in the dynamic SQL generation as well... like SQL Server uses TOP while MySql uses LIMIT and so forth.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search