db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-2917) Refactor DataTypeDescriptor and TypeDescriptor to result in cleaner code.
Date Tue, 02 Oct 2012 04:47:08 GMT

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

Mamta A. Satoor edited comment on DERBY-2917 at 10/2/12 3:45 PM:
-----------------------------------------------------------------

I do not believe Dan is currently working on this issue. Changing the ownerhsip to unassigned
in case some one else wants to pick it up.
                
      was (Author: mamtas):
    I do not believe Dan is working on this issue.
                  
> Refactor DataTypeDescriptor and TypeDescriptor to result in cleaner code.
> -------------------------------------------------------------------------
>
>                 Key: DERBY-2917
>                 URL: https://issues.apache.org/jira/browse/DERBY-2917
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services, SQL
>            Reporter: Daniel John Debrunner
>              Labels: derby_triage10_10
>
> TypeDescriptor ideally represents a catalog type (column in a table, parameter in a procedure
etc.)
> DataTypeDescriptor represents a runtime type
> Currently DataTypeDescriptor  extends (implements) TypeDescriptor , but the relationship
would be cleaner if DataTypeDescriptor  had a TypeDescriptor (but was not a TypeDescriptor).
> One can at the moment obtain a TypeDescriptor from a DataTypeDescriptor  using DataTypeDescriptor.getCatalogType()
but most code just treats DataTypeDescriptor   as a TypeDescriptor. This has lead to a couple
of issues:
> 1) When a routine's parameter/return type is written out a DataTypeDescriptor is written
to disk. This results in type information being repeated in the serialized form, thus increasing
the on-disk size of a Derby database.
> 2) Collation derivation is runtime only (all persistent types by definition have implicit
type) but the derivation is on the catalog Typedescriptor interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message