Normal syntax for LOB fields: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 19: | Line 19: | ||
<ul> | <ul> | ||
<li>The <var>Note</var> statement | <li>The <var>Note</var> statement | ||
<!-- need to research .. references to SIRLSAV, e.g., | <!-- need to research .. references to SIRLSAV, e.g., precluding Note is done in CMPJ. --> | ||
</ul> | </ul> | ||
This feature is disabled by setting the <var>LSTRLOB</var> system parameter to 0 (the default is 1). See the <var>[[LSTRLOB parameter#Description|LSTRLOB]]</var> description for further details. | |||
==Authorizing products== | ==Authorizing products== | ||
Revision as of 19:07, 22 June 2012
Starting with version V7R2 of Model 204, the Sirius Mods with Longstrings support allows use of most "normal" User Language syntax to access BLOB and CLOB fields.
For example:
DEFINE FIELD LONGSTUFF WITH BLOB ... begin store record LONGSTUFF = 'How now, brown cow?') end store fr print LONGSTUFF end for end
In this request, notice how the LOB field is updated directly (in the Store Record block) and retrieved directly (in the Print statement). In general, references to LOB fields can be made in this direct fashion, without utilizing the Universal Buffer.
There are a few exceptions to this; the following constructs do not allow such direct reference to the value of a LOB field:
- The Note statement
This feature is disabled by setting the LSTRLOB system parameter to 0 (the default is 1). See the LSTRLOB description for further details.
Authorizing products
Normal syntax for LOB fields is available to any customer who owns any of the following products:
- Fast/Unload User Language Interface
- Janus SOAP
- Janus Sockets
- Janus Web Server
- Sirius Functions