db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2746) If table only has fixed sized fields then derby should automatically set reserved space to 0.
Date Fri, 01 Jun 2007 21:07:16 GMT

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

Daniel John Debrunner updated DERBY-2746:
-----------------------------------------

    Affects Version/s:     (was: 10.2.2.0)
           Issue Type: Improvement  (was: New Feature)

I think this means fixed length in the on-disk format, not fixed length as seen by SQL, right?

E.g. these column definitions are *not* fixed length on disk:

          CHAR(10)
          INTEGER
          DECIMAL(6,2)

but these are
         INTEGER NOT NULL
         BIGINT NOT NULL

Ie. a column has to be not nullable for it to be fixed length on disk.

> If table only has fixed sized fields then derby should automatically set reserved space
to 0.
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2746
>                 URL: https://issues.apache.org/jira/browse/DERBY-2746
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Mike Matrigali
>            Priority: Minor
>
> At create table time the system should be able to tell if all the columns are fixed length,
and if the user has not set  reserved space it should be changed to 
> 0.  

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


Mime
View raw message