db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2257) Implementing the stored procedures called by the LOB related JDBC methods
Date Wed, 21 Feb 2007 08:30:05 GMT

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

V.Narayanan commented on DERBY-2257:

The following are a few questions I had highlighted in the txt file I had placed as an attachment
to the issue and for which I was requesting for advice. 

Placing the stored functions

1) Would it be a problem if the stored functions are visible to users
2) Where should the functions be placed? I had the following options
a) SYSFUN - did not seem the right place since all the functions here seemed to
called by the
b) SYSIBM - used for metadata functions
c) SYSCS_UTIL - I used this

Synchronization of locator related code inside EmbedConnection
would the rootConnection(EmbedConnection line no 157) shared across multiple
client connections? Would this result in a problem when adding code related to
adding locator to LOBReference mappings?

Currently I use a HashTable(which is a synchronized) and ensure synchronization
when I increment locator value

synchronized(getConnectionSynchronization()) {
  rootConnection.lobHTKey = rootConnection.lobHTKey + 1;
  return rootConnection.lobHTKey;

Is this required?
If it is required, is the synchronization I have done sufficient?

Temporary code in CLOBSETSTRING to add data in a Clob object
Since the set methods in the Clob interface have not yet been implemented and
for testing the Stored procedure code we need a Clob object populated with data
from the database to be added in the HashTable storing the locator to
LOBReference mapping in the HashTable in EmbedConnection the following two
step procedure has been followed while doing a 


1) Create a new Clob object with the supplied data
2) replace the Clob associated with LOCATOR in the HashTable with this
new Clob.

I will be posting a new patch handling test failures and comments I have received soon. 


> 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.

View raw message