Database connection. Each thread working with the database should have its own database connection.
More...
Database connection. Each thread working with the database should have its own database connection.
◆ Connection() [1/3]
| eXtremeDB.Connection.Connection |
( |
Database |
db | ) |
|
Constructor of the database connection.
- Parameters
-
◆ Connection() [2/3]
Copy constructor of the database connection.
- Parameters
-
| con | existed database connection |
◆ Connection() [3/3]
| eXtremeDB.Connection.Connection |
( |
Database |
db, |
|
|
byte[] |
context |
|
) |
| |
Constructor of the database connection with context.
- Parameters
-
| db | opened database |
| context | connection user defined context |
◆ CommitTransaction()
| virtual bool eXtremeDB.Connection.CommitTransaction |
( |
| ) |
|
|
virtual |
◆ Disconnect()
| virtual void eXtremeDB.Connection.Disconnect |
( |
| ) |
|
|
virtual |
◆ DiskFlush()
| void eXtremeDB.Connection.DiskFlush |
( |
| ) |
|
Flush to the disk all changes made by committed transactions. This method can be used to flush changes when the MCO_COMMIT_BUFFERED transaction policy is used.
- Returns
◆ Dispose()
| virtual void eXtremeDB.Connection.Dispose |
( |
| ) |
|
|
virtual |
◆ RollbackTransaction()
| virtual void eXtremeDB.Connection.RollbackTransaction |
( |
| ) |
|
|
virtual |
◆ SetCommitPolicy()
Set the transaction commit policy for this connection.
◆ StartTransaction() [1/2]
Start a transaction with the default priority and isolation level. (Nested transactions are supported.)
◆ StartTransaction() [2/2]
Start a transaction with the specified priority and isolation level. (Nested transactions are supported.)
Reimplemented in eXtremeDB.SqlLocalConnection.
The documentation for this class was generated from the following file:
- /home/trac/projects/eXtremeDB_8.0/supplements/netcore/src/netcore/exdbnet/Connection.cs