[
https://issues.apache.org/jira/browse/GROOVY-8397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273333#comment-16273333
]
Paul King commented on GROOVY-8397:
-----------------------------------
Okay, a followup question. Assuming this works, are you in a position to set
the new {{enableMetaDataChecking}} flag in your code? The current snapshot jar
has it temporarily set to disable extra checking but earlier requests were for
us to do some extra checking, so I think we'd want to default to have the flag
true.
> ORA-01000: maximum open cursors exceeded
> ----------------------------------------
>
> Key: GROOVY-8397
> URL: https://issues.apache.org/jira/browse/GROOVY-8397
> Project: Groovy
> Issue Type: Bug
> Components: SQL processing
> Affects Versions: 2.4.9, 2.4.10, 2.4.11, 2.4.12, 2.4.13
> Environment: Oracle 12.1.0.2.0
> Java 8 64bit
> Reporter: mgroovy
> Labels: cursor, oracle, sql
>
> * Evolving Oracle 12.1.0.2.0 DB schema with many objects from Groovy code
> based on Groovy Sql class worked up to groovy-2.4.7
> * From 2.4.9 up to 2.4.13 after some time during table creation/update schema
> evolver throws
> {code}
> java.sql.SQLException: ORA-01000: Maximale Anzahl offener Cursor überschritten
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
