[
https://issues.apache.org/jira/browse/IBATIS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571608#action_12571608
]
Venkatt Guhesan commented on IBATIS-142:
----------------------------------------
Hey Brian,
Your game plan sounds good. I'm looking forward to this fix. This will make the
configuration easier and compatible with the features available in JDK 1.4.
I'm a MySQL user but I occasionally use Postgres as well...
Since this feature is not available in Postgresql and pre-JDK 1.4, my
suggestion would be that if someone tried using this format against Postgresql
or a database that does not have this feature or a pre-1.4 JDK, then you can
query the
boolean java.sql.DatabaseMetaData.supportsGetGeneratedKeys() and if it returns
a false then you can throw an "UnsupportedFeatureException"
or if the JVM < 1.4 you can throw the same "UnsupportedFeatureException".
This can potentially eliminate some configuration errors.
> JDBC 3 Generated Keys Support
> -----------------------------
>
> Key: IBATIS-142
> URL: https://issues.apache.org/jira/browse/IBATIS-142
> Project: iBatis for Java
> Issue Type: Improvement
> Components: SQL Maps
> Reporter: Brandon Goodin
> Priority: Minor
>
> public int executeUpdate(String sql,int autoGeneratedKeys)
> public boolean execute(String sql,int autoGeneratedKeys)
> public ResultSet getGeneratedKeys()
> We should provide support for jdbc auto generated keys retrieval. This is
> only available in Java 1.4. So, we would have to throw an
> UnsupportedFeatureException if 1.3 or earlier was being used.
> Brandon
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
