Normal syntax for LOB fields: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 21: | Line 21: | ||
<!-- need to research .. references to SIRLSAV, e.g., preclucing Note is done in CMPJ. --> | <!-- need to research .. references to SIRLSAV, e.g., preclucing Note is done in CMPJ. --> | ||
</ul> | </ul> | ||
==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'' | |||
[[Category:User Language syntax enhancements]] | |||
Revision as of 03:08, 22 May 2012
Starting with version V7R2 of Model 204, when the Sirius Mods with Longstrings support, most "normal" User Language syntax can be used 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
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