DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30760>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30760 sql task handle pl/sql with ';' in pl/sql code. (patch) ------- Additional Comments From [EMAIL PROTECTED] 2004-08-23 14:59 ------- Usually PL/SQL code uses the "//" at begining of line to separate sql statements that must be processed in separate commits, but there is no restriction on pl/sql to have more than one DDL statement sent at once AFAIR (I may be wrong). With this in mind, have you tried just giving your file with delimeter="//" delimetertype="row" (check attribute names) and see what the Oracle JDBC driver will do? On the other hand, as every generation tool may do their particular quirks on the generated code, I see no reason why you could not have a step in your building process where the generatedfiles are preprocessed to produce something more friendly to a generic <sql/> task. I do not see why the <sql/> task needs to be maintained (and BC verified) against the whims of every generation tool that there is around. Alternatively you could subclass. Sql.java and have your own version specialized for your tools and maintained by you (as oppose to us). This is my main problem, who is goin to maintain all this special behaviors. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
