Asterisk - The Open Source Telephony Project
21.4.1
|
Data Fields | |
unsigned int | active:1 |
Is this record the current active transaction within the channel? Note that the active flag is really only necessary for statements which are triggered from the dialplan, as there isn't a direct correlation between multiple statements. Applications wishing to use transactions may simply perform each statement on the same odbc_obj, which keeps the transaction persistent. | |
unsigned int | forcecommit:1 |
unsigned int | isolation |
struct { | |
struct odbc_txn_frame * next | |
} | list |
struct { | |
struct odbc_txn_frame * next | |
} | list |
char | name [0] |
struct odbc_obj * | obj |
struct ast_channel * | owner |
Definition at line 115 of file res_odbc.c.
unsigned int forcecommit |
Should uncommitted transactions be auto-committed on handle release?
Definition at line 127 of file res_odbc.c.
unsigned int isolation |
Flags for how the DB should deal with data in other, uncommitted transactions
Definition at line 128 of file res_odbc.c.
char name |
Name of this transaction ID
Definition at line 129 of file res_odbc.c.
Referenced by PathSegment::__init__(), and PathSegment::get_child().
struct odbc_obj * obj |
Database handle within which transacted statements are run
Definition at line 118 of file res_odbc.c.