Jose Alberto Fernandez wrote:
Would be nice if you finish the submission so we can decide
if it should be part of core. And being able to point people to this
task.
Ok, will add it to my TODO list.
It maybe too late for 1.6.2 but none the less...
Np, I hope it can be of good use in any case (it has
: 06 July 2004 09:37
> To: [EMAIL PROTECTED]
> Subject: Re: SQLExec.class feedback attribute proposal
>
>
> Jose Alberto Fernandez wrote:
>
> > Had forgoten about this guy. Is it in the docs?
>
> Sorry, I don't understand... it's a patch. I have change
Jose Alberto Fernandez wrote:
Had forgoten about this guy. Is it in the docs?
Sorry, I don't understand... it's a patch. I have changed it based upon
feedback, and am waiting if it's basically ok so that I can add docs to
it and finish it off completely. :-)
[PATCH] Xml output for the SQL task
h
Had forgoten about this guy. Is it in the docs?
Maybe we should guide people to use this functionality.
Jose Alberto
> -Original Message-
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: 05 July 2004 16:34
> To: [EMAIL PROTECTED]
> Subject: Re: SQLExec
Jose Alberto Fernandez wrote:
...
To tell you the truth, I think the whole business of printing
results of queries using SQLTask was a mistake, and should have
been defined on a separate task that can do real XML output of
results that one can manipulate and format in watever fashion.
The current
Alberto
> -Original Message-
> From: Maksim Pakhutkin [mailto:[EMAIL PROTECTED]
> Sent: 05 July 2004 11:17
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: SQLExec.class feedback attribute proposal
>
>
> Hmmm... What I am actually proposing is that the task _no
Hmmm... What I am actually proposing is that the task _not_ do
something, that is, not print 'X rows affected'. I am not proposing
adding a new feature that is Oracle/PL-SQL specific. The 'X rows
affected' is generated by the SQLTask, not the RDBMS (although I think I
got a little confused when wri
Hmmm... What I am actually proposing is that the task _not_ do
something, that is, not print 'X rows affected'. I am not proposing
adding a new feature that is Oracle/PL-SQL specific. The 'X rows
affected' is generated by the SQLTask, not the RDBMS (although I think I
got a little confused when wri
I think these increasing types of functionality have
been asked before for the SQLTask.
I really think people are asking for the SQLTask to be as flexible
as a scripting language (like sqlplus or PL/SQL) which is not
what the task how the task was originally conceived.
As a result there are more
