Scalable Database Server, HiRDB Version 8 Description
When BLOB or BINARY data is updated after new data has been added to a registered BLOB or BINARY data item, or when an entire BLOB or BINARY data item is retrieved as the result of BLOB or BINARY data being searched, both the server and the client must allocate a large amount of memory for the BLOB or BINARY data, putting a strain on memory resources.
Use of the BLOB and BINARY data addition update and partial extraction facility allows you to avoid straining memory resources, because it allocates only the memory required for the actual amount of BLOB or BINARY data being added or extracted.
However, for BINARY data, the definition length must be 32,001 bytes or greater.
For details about the BLOB and BINARY data addition update and partial extraction facility, see the HiRDB Version 8 UAP Development Guide.
A single BLOB data item is stored across a number of files. Figure 6-18 shows an example of BLOB data addition updating.
Figure 6-18 Example of BLOB data addition updating
An area in file 2 is extracted from the BLOB data in column C2 of row A that was stored using BLOB data addition updating. Figure 6-19 shows an example of BLOB data partial extraction.
Figure 6-19 Example of BLOB data partial extraction
All Rights Reserved. Copyright (C) 2007, Hitachi, Ltd.