[DERBY-2540] Restructure code for Blob/Clob length in client to prepare for locator implementation

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.3.1.4
• Component/s: Network Client
• Assignee: Oystein Grovlen
• Reporter: Oystein Grovlen
• Created: 11/Apr/07 12:17
• Updated: 11/Jul/07 08:11
• Resolved: 18/Apr/07 16:20

Description

In order to prepare for the locator-based implementation, I want to restructure the code for getting the length of LOBs.
Currently, the LOB class has a protected field sqlLength_ that will contain the length of the LOB, if known. Currently, it is always known as long as the LOB has been materialized. However, when locators are introduced, the length may have to be fetched from the server the first time it is needed. With the current implementation, where sqlLength_ is accessed directly by many classes in the package, it will become very difficult to keep track of whether one needs to fetch the length from the server or not.

I will change the implementation to make Lob.sqlLength_ private and add access methods to get and set its value. (A good thing in itself IMHO). If the length is unknown, the LOB will be materialized to get the length.