[
https://issues.apache.org/jira/browse/DERBY-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3430:
----------------------------------
Fix Version/s: 10.4.0.0
> Inconsistency in JDBC autogen APIs between Connection.prepareStatement(...)
> and Statement.execute(...)
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3430
> URL: https://issues.apache.org/jira/browse/DERBY-3430
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.3.1.4, 10.4.0.0
> Reporter: A B
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.4.0.0
>
> Attachments: derby-3430_diff.txt
>
>
> In EmbedStatement.java the execute(String, String[]), execute(String, int[]),
> executeUpdate(String, String[]), and executeUpdate(String, int[]) methods
> treat a 0-length array to mean NO_GENERATED_KEYS. But in
> EmbedConnection.java the prepareStatement(String, String[]) and
> prepareStatement(String, int[]) methods treat a 0-length array to mean
> RETURN_GENERATED_KEYS. For the sake of consistency, the two classes should
> treat 0-length arrays in the same way--which probably means changing
> EmbedConnection to match EmbedStatement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
