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=19921>. 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=19921 Optional replace of properties in SQL task ------- Additional Comments From [EMAIL PROTECTED] 2003-05-16 13:29 ------- The escaping works OK for many, but not all scenarios. The replacement of the properties is a useful feature, but it is still a sideeffect, which isn't directly SQL related. I don't want to remove the feature, I just want to be able to turn it off. The proposed change does not break existing code, it is basically just one extra if-statement. If I was to use the escaping strategy, that would mean I had to add a $ just so that ANT can remove it. There are some CPU cycles to gain, by doing less. The escaping does not work with Oracle wrapped (scrambled code) files. Oracle requires the file to be unmodified, which rules out escaping. SQLExec works great with Oracle wrapped files (which I think is cool), as long as there are no ANT properties. Why not take it all the way?
