G
Guest
Hi;
I am finding the following very frustrating and if someone could just tell
me why - I think it would be less frustrating:
1) Why is setting parameters in ADO.NET vendor specific? JDBC has had this
vendor neutral since version 1.0.
2) Why no simple vendor independent way to get the value of an
auto-generated primary key? This has been a need forever and instead everyone
has to implement this on their own.
3) Why no vendor independent way to get all tables, views, & stored
procedures in a database and to get all columns in a table/view? OleDb has
this but not ADO.NET.
4) Why is DbProviderFactory.CreateDataSourceEnumerator() only provided for
SqlServer? The OleDb info is in the registry and the Oracle info is
(partially) in the root Oracle config file.
5) Why only 2 clients? Back in the ODBC and OleDb days MS was doing
everything it could to have tons of clients shipped with Windows. Now it's
SqlServer, Oracle, and the two bridge clients (OleDb & ODBC)?
If someone at MS could just explain why...
I am finding the following very frustrating and if someone could just tell
me why - I think it would be less frustrating:
1) Why is setting parameters in ADO.NET vendor specific? JDBC has had this
vendor neutral since version 1.0.
2) Why no simple vendor independent way to get the value of an
auto-generated primary key? This has been a need forever and instead everyone
has to implement this on their own.
3) Why no vendor independent way to get all tables, views, & stored
procedures in a database and to get all columns in a table/view? OleDb has
this but not ADO.NET.
4) Why is DbProviderFactory.CreateDataSourceEnumerator() only provided for
SqlServer? The OleDb info is in the registry and the Oracle info is
(partially) in the root Oracle config file.
5) Why only 2 clients? Back in the ODBC and OleDb days MS was doing
everything it could to have tons of clients shipped with Windows. Now it's
SqlServer, Oracle, and the two bridge clients (OleDb & ODBC)?
If someone at MS could just explain why...