Tutorial: Interoperability and Microsoft .NET
Wide latitude in the specifications for ADO.NET data providers may limit interoperability across databases
Microsoft's decision to have a flexible specification for the way that data providers access databases means that the implementations of ADO.NET data providers for different databases can vary widely. Even when using the Common Model for ADO.NET 2.0 to write provider independent code, programmers who switch to different data stores must expect to change their code, or even their coding logic.
Progress DataDirect Connect is known for our focus on interoperability. By using a common approach, we keep the interfaces and functionality the same for all of our ADO.NET data providers. We add interoperability to our data providers by:
- Providing support for ODBC/JDBC SQL escapes for executing stored procedures and standardized SQL statements
- Providing standardized parameter markers
- Providing a standard mechanism to specify arrays of parameters (bulk inserts and updates)
- Providing standard error code mapping for database-specific errors
- Providing support for stored procedures
Topics described (with code samples) in this material (click to review complete example):
