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=38245>. 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=38245 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-18 17:51 ------- (In reply to comment #6) > -HSQLDB builds in gump and is the easiest to test against. OK, unfortunately another learning curve for me... > -Right now we just need to test that we can make SQL commands and transactions > from inline text and files. Understand this one. > -Test the property expansion stuff I just added OK, I need to look at this. > -see what happens when an invalid command is issued (ie does it fail) Well, this depends on the "continue on error" setting (I forget the attribute at the moment) doesn't it? > I don't have any opinion on SQL decorators; I have only just started using the > task. For testing, I'd point you at dbunit of course. I can discuss this with you offline; For Oracle, there are several posted modifications of the SQL task that allow for turning on "dbms_output" prior to executing the command and retrieving its "output" after the command has executed - seems to be almost tailor made for a SQL task "decorator" that is instantiated when Oracle is specified. > We may want a specific JDBC datatype that can be reused; containing all the > jdbc > options, multiple sql tasks can then share it. I'll need more explanation here - is this a test fixture you're referring to? Ken -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
