Represents an open connection to a database. This class cannot be inherited.
public ref class OracleConnection sealed : System::ComponentModel::Component, ICloneable, IDisposable, System::Data::IDbConnection
public ref class OracleConnection sealed : System::Data::Common::DbConnection, ICloneable
public sealed class OracleConnection : System.ComponentModel.Component, ICloneable, IDisposable, System.Data.IDbConnection
public sealed class OracleConnection : System.Data.Common.DbConnection, ICloneable
[System.Obsolete("OracleConnection has been deprecated. http://go.microsoft.com/fwlink/?LinkID=144260", false)]
public sealed class OracleConnection : System.Data.Common.DbConnection, ICloneable
type OracleConnection = class
inherit Component
interface ICloneable
interface IDbConnection
interface IDisposable
type OracleConnection = class
inherit DbConnection
interface ICloneable
[<System.Obsolete("OracleConnection has been deprecated. http://go.microsoft.com/fwlink/?LinkID=144260", false)>]
type OracleConnection = class
inherit DbConnection
interface ICloneable
Public NotInheritable Class OracleConnection
Inherits Component
Implements ICloneable, IDbConnection, IDisposable
Public NotInheritable Class OracleConnection
Inherits DbConnection
Implements ICloneable
This type is deprecated and will be removed in a future version of .NET Framework. For more information, see Oracle and ADO.NET.
An OracleConnection object represents a unique connection to an Oracle database. In the case of a client/server database system, it is equivalent to a network connection to the server.
An application that creates an instance of the OracleConnection object can set declarative or imperative security demands that require all direct and indirect callers to have adequate permission to the code. OracleConnection creates security demands by using the OraclePermission object. Users can verify that their code has adequate permissions by using the OraclePermissionAttribute object. Users and administrators can also use the Code Access Security Policy Tool (Caspol.exe) to modify security policy at the machine, user, and enterprise levels. For more information, see Security.
Note
Unlike the Connection object in the other .NET Framework data providers (SQL Server, OLE DB, and ODBC), OracleConnection does not support a ConnectionTimeout property. Setting a connection time-out either as a property or in the connection string has no effect, and the value returned is always zero. OracleConnection also does not support a Database property or a ChangeDatabase method.
If the OracleConnection object goes out of scope, it remains open. Therefore, you should always close OracleConnection objects by calling Close or Dispose, or by using the OracleConnection object within a Using
statement. Otherwise, the garbage collection might not free them immediately. Such delays can cause errors if the maximum number of connections is reached while a number of connections are waiting to be deleted by the garbage collector. By contrast, closing the connections by calling Close uses native resources more efficiently, enhancing scalability and improving overall application performance. To ensure that connections are always closed, open the connection inside of a Using
block.
Note
To deploy high-performance applications, you often need to use connection pooling. However, when you use the .NET Framework Data Provider for Oracle, you do not need to enable connection pooling because the provider manages this automatically.
Constructors Properties Methods Events Explicit Interface Implementations See alsoRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4