[
https://issues.apache.org/jira/browse/DERBY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474930
]
Knut Anders Hatlen commented on DERBY-2347:
-------------------------------------------
I don't think the DRDA protocol allows pre-fetching when the result contains
LOBs. I haven't checked what the spec says, but I found these comments in
DRDAConnThread:
processCommands():
if (stmt.getQryprctyp()
== CodePoint.LMTBLKPRC &&
stmt.getQryrowset() != 0) {
// The DRDA
spec allows us to send
// QRYDTA here
if there are no LOB
// columns.
parseEXCSQLSTT():
/* Currently, if LMTBLKPRC is used, a pre-condition is
that no lob columns.
* But in the future, when we do support LOB in
LMTBLKPRC, the drda spec still
* does not allow LOB to be sent with OPNQRYRM. So
this "if" here will have
* to add "no lob columns".
*/
if (stmt.getQryprctyp() == CodePoint.LMTBLKPRC)
writeQRYDTA(stmt);
> Add code to support request and return of locators over DRDA
> ------------------------------------------------------------
>
> Key: DERBY-2347
> URL: https://issues.apache.org/jira/browse/DERBY-2347
> Project: Derby
> Issue Type: Sub-task
> Components: Network Client, Network Server
> Reporter: Øystein Grøvlen
> Assigned To: Øystein Grøvlen
> Attachments: DERBY-2347-v1.diff, DERBY-2347.diff
>
>
> - Make the client able to send DRDA OUTOVR commands to request locators from
> Network Server.
> - Make the network server send locators instead of LOB values if locators has
> been
> requested.
> This JIRA will not activate the code that request locators since the client
> is not yet able to handle locators.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
