[ http://issues.apache.org/jira/browse/DERBY-208?page=comments#action_12460017 ] Øystein Grøvlen commented on DERBY-208: ---------------------------------------
Great work with the thorough use-cases, Fernanda. I suggest to go for an implementations where locators work on copies and not directly on the LOBs. Working directly on a LOB can change the behavior of current applications since updates may occur without a call to updateRow(). Hence, applications which sets parameters and then for some reason skips updateRow(), will experience a changed behavior. Also, it seems like the infrastructure for working on a copy will be needed anyway in order to temporarily store LOBs that have not yet been assigned to a row. > Add support to retrieve lobs for Network Server by locator rather than > matierializing the LOB > --------------------------------------------------------------------------------------------- > > Key: DERBY-208 > URL: http://issues.apache.org/jira/browse/DERBY-208 > Project: Derby > Issue Type: New Feature > Components: Network Server > Affects Versions: 10.1.1.0 > Reporter: Kathey Marsden > Attachments: LOBLocator.pdf > > > Currently Network Server materializes all LOB objects. LOB locator support > is part of the DRDA spec so could be added to network server. See > http://www.opengroup.org/dbiop/ > It is not clear if SQL Support for LOB locators would also be required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
