Porting Client Application to .NET Stored Procedure

All classes and class members provide the same functionality for both client applications and .NET stored procedures, unless it is otherwise stated.

Table 5-1 lists those classes or class members that have different behavior depending on whether or not they are used in a client application or in a .NET stored procedure.

Column Headings

The column headings for this table are:

Client application: The client application.

Implicit connection: The implicit database connections in a .NET stored procedure.

Explicit connection: The explicit user connections in a .NET stored procedure.

Table 5-1 API Support Comparison Between Client Application and .NET Stored Procedure

Class or Class Members	Client Application	Implicit Connection/Explicit Connection
OnChangeEventHandler Delegate -all members	Yes	No/No
OracleDependency Class -all members	Yes	No/No
OracleNotificationEventArgs Class -all members	Yes	No/No
OracleNotificationRequest Class -all members	Yes	No/No
OracleFailoverEventArgs Class -all members	Yes	No/No
OracleFailoverEventHandler Delegate -all members	Yes	No/No
OracleTransaction Class -all members	Yes	No/No
OracleCommand Class -Transaction Property	Yes	No: Always returns null /No: Always returns null.
OracleConnection Class -ConnectionTimeout Property -DataSource Property -BeginTransaction Method -ChangeDatabase Method -Clone Method -EnlistDistributedTransaction Method -OpenWithNewPassword(String) Method -Failover Event -OracleFailoverEventHandler Delegate	Yes Yes Yes No Yes Yes Yes Yes Yes	Yes: Implicit database connection always returns `0`/Yes Yes: Implicit database connection always returns an empty string/Yes No/Yes No/No No/Yes No/No No/Yes No/No No/No
ODP.NET Enumerations -FailoverEvent Enumeration -FailoverReturnCode Enumeration -FailoverType Enumeration -OracleNotificationInfo Enumeration -OracleNotificationSource Enumeration -OracleNotificationType Enumeration	Yes Yes Yes Yes Yes Yes	No/No No/No No/No No/No No/No No/No