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=28681>. 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=28681 [PATCH] Xml output for the SQL task ------- Additional Comments From [EMAIL PROTECTED] 2004-05-06 15:34 ------- Just to make my point more clear on why I think we are going in the wrong direccion: In your current proposal, your nested XML output requires a certain order for the query, in order for nesting to be processed correctly. So what does happens if I have several queries in my <sql/>? Do they all are required to look the same? You see, with csv or with non-nested XML there is no assumption about the shape of the query. Hence it does not matter if you are executing one query or 100 queries. But if now we want to be able to process the output (and since SQL can execute multiple queries in the same transaction, etc.), we would need to provide the formatting rules (or the extractor) in a query by query basis. When you look at all this issues, then you see that it is not that simple. - You probably need to be able to apply your extractor in a query by query basis. - If you want to be able to write generic extractors, (e.g., velocity) then you need to be able to specify the velocity script which may be complex. - If you want a scripted extractor, you may need to be able to include the text of the script. Something like: <sql ....> <transaction> <extractor class="foo.my.Extractor"> <formatter> </formatter> <query> select a, b from c, d where c.a = d.b </query> </extractor> </transaction> </sql> Now when you see all what is needed to do it properly, then it makes much more sence to use a separate task for all this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
