[
https://issues.apache.org/jira/browse/DDLUTILS-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470981
]
Mike Perham commented on DDLUTILS-154:
--------------------------------------
We are using DdlUtils to generate sql at build time for a number of different
database platforms we support (mysql, db2, etc). This sql is loaded at runtime
if the database is detected to be empty in order to create the tables. We are
testing oracle for the first time and running into this issue.
>From your dbmotive link:
bq. Alternatively, there is a problem with the Oracle 10g JDBC driver when
trying to use the :NEW or :OLD Oracle keywords in a PreparedStatement.
Ok, this looks like an Oracle bug/feature. I should be able to work around it
in our SqlLoader class. Issue (hopefully) resolved.
> Autoincrementing columns broken on Oracle10?
> --------------------------------------------
>
> Key: DDLUTILS-154
> URL: https://issues.apache.org/jira/browse/DDLUTILS-154
> Project: DdlUtils
> Issue Type: Bug
> Components: Core - Oracle
> Affects Versions: 1.0
> Environment: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0
> Reporter: Mike Perham
> Assigned To: Thomas Dudziak
>
> java.lang.RuntimeException: Unable to execute SQL with message 'Missing IN or
> OUT parameter at index:: 1' and code 17041/null:
> CREATE OR REPLACE TRIGGER trg_w_inboxmsg_id BEFORE INSERT ON w_inboxmsg FOR
> EACH ROW WHEN (new.id IS NULL)
> BEGIN SELECT seq_w_inboxmsg_id.nextval INTO :new.id FROM dual; END;;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
