DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10719>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10719 Files processed under SQL task are hacked ------- Additional Comments From [EMAIL PROTECTED] 2002-07-27 13:51 ------- Well, I was one of the original authors of this task and the reason why comments were stripped was that different RDBMSs use different types of comments. Although this may seem unimportant for people that are committed to support only one DB, it is an important issue for those projects that try to be DB agnostic. The idea beeing that ANT should treat the DB the same way it treats an OS, which in escence is what JDBC is all about. Maybe the solution to this issue (and I am not sure if the original code had provisions for that) is to allow defining which types of comments, <sql> should strip, if any. This would allow people writing multiDB scripts to write comments in the file but knowing that they will not be a problem when deploying on different DBs. At the same time people will be able to preserve comments using DB specific syntax if they please. It would be nice if DB comments could be translated to the DB specific syntax, but I am not sure if this info is available from the JDBC API. Whatever the solution, one should be able to write a well documented DB script that can be executed asis on all major RDBMSs: oracle, mssql, mysql, posgress, DB2, etc. (As long as they use SQL92 syntax, of course). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
