23.10.2012 Views

Openedge Data Management: SQL Reference - Product ...

Openedge Data Management: SQL Reference - Product ...

Openedge Data Management: SQL Reference - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Data</strong> types<br />

200<br />

LVARBINARY ( length )<br />

Corresponds to an arbitrarily long byte array with the maximum length defined by the<br />

amount of available disk storage up to 1,073,741,823. A BLOB is an object of data type<br />

LVARBINARY.<br />

Maximum length for VARBINARY<br />

The maximum length of the VARBINARY data type depends on:<br />

• The number of columns in a table — More columns in a table further limits the length<br />

of VARBINARY data.<br />

• When a table was created — Tables created earlier can support longer VARBINARY data<br />

than tables created later.<br />

LVARBINARY limitations<br />

Current limitations for LVARBINARY support are as follows:<br />

• LVARBINARY data type will only be accessible from the <strong>SQL</strong> Engine. LVARBINARY data<br />

columns added to tables created by the ABL (Advanced Business Language) are not<br />

visible to the ABL.<br />

• LVARBINARY data columns cannot be part of an index.<br />

• LVARBINARY data columns cannot be used for variables or as parameters in stored<br />

procedures.<br />

• Comparison operations are not supported on LVARBINARY columns. Comparison<br />

operations between LVARBINARY columns are not supported. Comparison operations<br />

between LVARBINARY columns and columns of other data types are not supported.<br />

• Conversion, aggregate, and scalar functions are disallowed on this data type.<br />

• LVARBINARY does not have National Language Support (NLS).<br />

Language support for LVARBINARY<br />

This data type has normal column functionality except for the following exceptions:<br />

• A column of data type LVARBINARY is not a valid column name in a CREATE INDEX<br />

statement.<br />

• When issuing a CREATE TABLE statement, a valid data type for the column definitions is<br />

LVARBINARY. However, LVARBINARY does not allow the column constraints of PRIMARY<br />

KEY, FOREIGN KEY, UNIQUE, REFERENCES, and CHECK.<br />

• When creating a table with a column of data type LVARBINARY, place the table in a new<br />

AREA.<br />

• The VALUES option on the INSERT statement is not valid for the LVARBINARY data type.<br />

• In a SELECT statement, a WHERE, GROUP BY, HAVING, or ORDER BY clause cannot use a<br />

column of data type LVARBINARY.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!