db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4918) Minor refactoring of SPSDescriptor
Date Fri, 25 Feb 2011 21:13:21 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan closed DERBY-4918.
----------------------------------

    Resolution: Fixed

Closing issue.

> Minor refactoring of SPSDescriptor
> ----------------------------------
>
>                 Key: DERBY-4918
>                 URL: https://issues.apache.org/jira/browse/DERBY-4918
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.8.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.8.0.0
>
>         Attachments: derby-4918-1a-misc.diff, derby-4918-1a-misc.stat, derby-4918-2a-remove_setUUID.diff,
derby-4918-2b-remove_setUUID.diff
>
>
> The class SPSDescriptor is kind of hard to understand, and doesn't quite follow the pattern
used by other tuple descriptors. Parts of the code don't agree with the documentation (i.e.
SPS_TYPE_TRIGGER marked as not implemented)
> This issue tracks work to make the class easier to understand and to modify.
> The critical part that may need to be changed is the use of synchronized (this). The
problem is that database locks are obtained within the critical regions, and in some special
cases this causes deadlocks. I'm not yet certain this can be fixed at this level (only), but
I'll continue investigation.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message