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 15:31 ------- well, i'm not trying to make your life difficult, and i'm deffinetly not trying to turn the SQLExec.java into some monster that handles "the whims of every generation tool that there is around". I do however have issues with the fact that the task is not recognizing valid sql. The stored procedure example i gave is valid sql, and i can take that sql (unmodified) to any other database independent tool and run it with no problems. But i take that very same sql and give it to the <sql> task and it fails. To me that is a flaw in the task, not the tool that generated the statement nor the statement itself. Now, i don't mind doing the leg work and testing this against the 4 databases i mentioned, but won't be able to do so until later this year. I just assumed that the developers maintaining the task had unit tests for ensuring the functionality and compatability of their code and that it wouldn't be too difficult to run those tests with my patch or a similar patch created with the same goal in mind. If you still think this is a one off (even though valid sql statements fail), then i will stop harrassing you and just spawn off my own task. I am surprised that others are not complaining about this, with the exception of a couple mailing list posts i found. I REALLY DO appreciate you taking the time to consider this and giving me good responses on you opinions why you don't see a need for this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
