db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-1735) Large number of rows in a VALUES clause (e.g. for an INSERT) can result in a StackOverflowError
Date Mon, 05 Nov 2012 13:34:12 GMT

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

Rick Hillegas updated DERBY-1735:
---------------------------------

    Bug behavior facts: Seen in production

Marking as "Seen in production" because of the duplicate issue DERBY-5981.
                
> Large number of rows in a VALUES clause (e.g. for an INSERT) can result in a StackOverflowError
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1735
>                 URL: https://issues.apache.org/jira/browse/DERBY-1735
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.1.6, 10.3.1.4
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>              Labels: derby_triage10_5_2
>
> With DERBY-766 / DERBY-1714extending the limit for number of rows in a VALUES clause
the next error seen is a stack overflow.
> issue can be seen by increasing the number of rows in the testInsertValues portion of
largeCodeGen

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