You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/14 20:18:20 UTC

[jira] [Updated] (DERBY-5781) Investigate lifting the limit on the number of columns in a Derby table

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

Rick Hillegas updated DERBY-5781:
---------------------------------

    Affects Version/s: 10.10.1.2
        Fix Version/s:     (was: 10.10.1.2)
    
> Investigate lifting the limit on the number of columns in a Derby table
> -----------------------------------------------------------------------
>
>                 Key: DERBY-5781
>                 URL: https://issues.apache.org/jira/browse/DERBY-5781
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.10.1.2
>            Reporter: Rick Hillegas
>
> Derby tables are limited to 1012 columns. This arbitrary limit is not found in the SQL Standard and is the value of Limits.DB2_MAX_ELEMENTS_IN_SELECT_LIST. We should investigate lifting this limit based on user demand: http://old.nabble.com/limit-on-the-number-of-columns-to33901308.html#a33901308

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