[ 
https://issues.apache.org/jira/browse/DERBY-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474973
 ] 

V.Narayanan commented on DERBY-2257:
------------------------------------

Thank you for the comments again,

The situation you have pointed out is when the database is read-only. This 
would mean that the create procedure calls would fail. The server should be 
able to detect this and will not send locators. It will send the LOB instead 
and the client should be intelligent enough to handle this. The comments on 
Derby-2347 also point towards the same. 

I have copied the following from comments on - Derby -2347 today morning
------------------------------------------------------------------------------------------------------
"Anyhow, the client will be made so that it also handles receiving LOBs when it 
had requested locators.  "

If the procedures are created the client will receive locators. Otherwise it 
will receive LOB's and will handle that. 

Even if we decide not to do it the soft upgrade by creating all the procedures 
we would need a mechanism that would provide the functionality without 
locators. We can use that same when the procedures are not there and resort to 
the locator implementation if we were able to create the procedures.

Note that this is still the way I think can be done. I do not have code to 
support what I propose at this juncture but will come up with it in the upgrade 
JIRA issue.

> Implementing the stored procedures called by the LOB related JDBC methods
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2257
>                 URL: https://issues.apache.org/jira/browse/DERBY-2257
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>         Environment: All environments
>            Reporter: V.Narayanan
>         Assigned To: V.Narayanan
>         Attachments: Expln_StoredProc_LOB.txt, Expln_StoredProc_LOB_v2.txt, 
> StoredProcedures_v1.diff, StoredProcedures_v1.stat, StoredProcedures_v2.diff, 
> StoredProcedures_v2.stat
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to