tblLVST_CustomApplicationInteractionData

Table Description:

Custom data applicable to a single interaction in a 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

InteractionID

INTEGER

N/A

N/A

tblLVST_CallInteractions

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:

CustomApplicationInteractionDataID

Foreign keys relationships:

Foreign key Reference table Reference key

InteractionID

tblLVST_CallInteractions

InteractionID

 
Foreign key Reference table Reference key

UserDefinedType

tblLVST_CustomApplicationInteractionData_cUserDefinedType

ConstantValue

Column Descriptions and Constraints:

InteractionID

Description:
Foreign key to tblLVST_CallInteractions. Identifies the interaction this item belongs to.
Constraint Name:
N/A
Constraint Description:
N/A

UserDefinedType

Description:
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.
Constraint Name:
N/A
Constraint Description:
N/A

UserDefinedName

Description:
The name, if any, of the data stored here.
Constraint Name:
N/A
Constraint Description:
N/A

UserData

Description:
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. You must *always* use sqlite_encode_binary and sqlite_decode_binary in this field, to store and retrieve binary data.
Constraint Name:
N/A
Constraint Description:
N/A

Table Constraints:

Constraint Name: N/A
Constraint Description:
N/A
Columns related:
N/A