Collaboration diagram for odbc_txn_frame:

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
char	name [0]
struct odbc_obj *	obj
struct ast_channel *	owner

Field Documentation

unsigned int active

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.

Definition at line 172 of file res_odbc.c.

Referenced by find_transaction(), and mark_transaction_active().

unsigned int forcecommit

Should uncommitted transactions be auto-committed on handle release?

Definition at line 173 of file res_odbc.c.

Referenced by find_transaction(), odbc_release_obj2(), acf_transaction_read(), and acf_transaction_write().

unsigned int isolation

Flags for how the DB should deal with data in other, uncommitted transactions

Definition at line 174 of file res_odbc.c.

Referenced by find_transaction(), acf_transaction_read(), and acf_transaction_write().

struct { ... } list

char name[0]