[
https://issues.apache.org/jira/browse/DERBY-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539393
]
Kathey Marsden commented on DERBY-176:
--
After merging change 377609, I see a different error at 99,000
[
https://issues.apache.org/jira/browse/DERBY-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538116
]
Kathey Marsden commented on DERBY-176:
--
I received a request to backport this change to 10.1. I will be looking
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_12359747 ]
Daniel John Debrunner commented on DERBY-176:
-
I have code that traps most limit execeed errors and throws a statement too
complex error. I will submit this soon,
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_12359697 ]
Kathey Marsden commented on DERBY-176:
--
While we would like to continue to make progress on DERBY-176, there will
likely always be some upper bound on the complexity of
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_12359176 ]
Daniel John Debrunner commented on DERBY-176:
-
Other commits for this issue:
160444 - Add pop() method to byte code compiler. (incorrect makred for
Derby-167)
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_62384 ]
Daniel John Debrunner commented on DERBY-176:
-
svn revision 160426
Added checks when the generated class file's format is created to ensure the
structure is not
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_62393 ]
Daniel John Debrunner commented on DERBY-176:
-
A modified version of Kathey's test case has been committed into the trunk
Derby throws ERROR XBCM1: Java linkage
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_62286 ]
Daniel John Debrunner commented on DERBY-176:
-
Kathey Marsden and myself made a number of changes in IBM's Cloudscape 5.1
codeline to make progress in this area
[
http://issues.apache.org/jira/browse/DERBY-176?page=comments#action_61425 ]
Jack Klebanoff commented on DERBY-176:
--
I think that there are 3 approaches to solving the problem of the Derby code
generator exceeding JVM class size limits:
1.