[ http://issues.apache.org/jira/browse/DERBY-208?page=comments#action_12459690 ] Daniel John Debrunner commented on DERBY-208: ---------------------------------------------
Reading the result columns in order is actually recommended by the JDBC javadoc for ResultSet for portability, so while it would be good to not have this restriction, I think it would be ok to require it in some form if it made a streaming/locator LOB implementation easier. > 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
