 |
 |
|
|
       |
|||
| SQL_Vector_type |
|
|
|
|||||||||||
|
|||||||||||
The SQL_Vector_type OMX component, in conjunction with SQL_Array_type and SQL_Handle_type OMX components, allows you to access an ODBC-compliant database from within an OmniMark program. The SQL_Vector_type OMX component acts as an interface between OmniMark and ODBC one-dimensional arrays.
The OmniMark ODBC dynamic link library file ("omodbc.dll" or "omodbc.so") creates the SQL_Vector_type OMX component. The related include file ("omodbc.xin") defines the interface to that component. To use SQL_Vector_type in your program, you must include the following declaration and include statement in your program:
include "omodbc.xin"
Within your program, you can create as many instances of the SQL_Vector_type component as you require by declaring global and local variables of type "SQL_Vector_type". For example:
; required declaration and include statements
include "omodbc.xin"
; global SQL_Vector_type declarations
global SQL_Vector_type my-sqlvector-1
global SQL_Vector_type my-sqlvector-2
process
; local SQL_Vector_type declarations
local SQL_Vector_type my-sqlvector-3
local SQL_Vector_type my-sqlvector-4
Once you have declared your SQL_Vector_type variables, you manipulate these variables using the functions in the OmniMark ODBC function library.
The SQL_Vector_type OMX component is not copyable. This means that when you set the value of one SQL_Vector_type OMX variable to the value of another SQL_Vector_type OMX variable, you end up with two variables both pointing at the same external object. You are able to manipulate both variables, but you are performing those manipulations on the same external object, whether you use the original SQL_Vector_type OMX variable or its copy.
| ---- |
