tblLVST_CustomApplicationCallData

Table Description:

Custom data applicable to an entire call. This table is meant to allow arbitrary extensions to the Tuner database. The table is *untouched* by the regular Tuner system; it is up to the developer to maintain this table correctly. If you attempt to store binary data in UserData, you *must* use sqlite_encode_binary to encode the binary data, and sqlite_decode_binary to transform the data back to it's binary form.

Table structure:

Column Name	Data Type	Data Length	Default Value	See Also
CallID	INTEGER	N/A	N/A	tblVST_Calls
UserDefinedType	INTEGER	N/A	N/A	N/A
UserDefinedName	VARCHAR(900)	N/A	N/A	N/A
UserData	TEXT	N/A	N/A	N/A

Primary Keys:

CustomApplicationCallDataID

Foreign Key	Reference Table	Reference Key
CallID	tblLVST_Calls	CallID
UserDefinedType	tblLVST_CustomApplicationCallData_cUserDefinedType	ConstantValue

Column Descriptions and Constraints:

Column	Description	Constraint Name	Constraint Description
CallID	Foreign key to tblLVST_Calls. Identifies the call this item belongs to.	N/A	N/A
UserDefinedType	The type of the data. The type maps to a ConstantValue in tblLVST_ApplicationInteractionData_cUserDefinedType via a ConstantName. (UDT_LUMENVOX, 0) is reserved for LumenVox use.	N/A	N/A
UserDefinedName	The name, if any, of the data stored here.	N/A	N/A
UserData	The values of this entry. For actual text data, you must ensure that the data is single-quote safe. If this is binary data, you *must* take care to prevent single quotes and null bytes from intefering with storage. SQLite stores *everything* as a string, so if you have random null bytes laying around, you will never get the full data stored, or be able to retrieve it its entirety. I recommend that you *always* use sqlite_encode_binary and sqlite_decode_binary in this field.	N/A	N/A

Table Constraints:

Constraint Name	Constraint Description	Columns Related
N/A	N/A	N/A