Tomas,
Maybe I can be a little more explicit in my desires. I did not explore the
feasibility technically, but was just hoping that something could be
displayed.
For example, if I define the SQL task as such:
<sql connstring="Provider=SQLOLEDB;User ID=sa;Password=dil.bert;Initial
Catalog=master;Data Source=${db.server}"
transaction="false"
delimiter=";"
delimstyle="Normal"
print="true"
output="${build.latest.portal.db.dir}\restoreDbResults.txt"
verbose="${isVerbose}">
SELECT *
FROM Users
WHERE ID = 'Joe'
</sql>
If ${isVerbose} = true, then I would see something like this:
[sql] Executing SQL statement against master on ${db.server}
[sql]
[sql] User ID: sa
[sql] Provider: SQLOLEDB
[sql]
[sql] Output: ${build.latest.portal.db.dir}\restoreDbResults.txt
[sql]
[sql] c:\projects\WebServices\WwService\bin\log4net.dll
[sql] SELECT *
[sql] FROM Users
[sql] WHERE ID = 'Joe'
[sql]
[sql] 14 records affected (or error message)
If ${isVerbose} = false, then I would see something like this:
[sql] Executing SQL statement against master on ${db.server}
[sql] 14 records affected (or error message)
I guess this is what I was thinking. I am sure there are technical hurdles
to do something like this. I guess I could <echo> all of this, but then I
would feel that my build script would be "cluttered". I know that I could
put an 'if' on the echo task...
I see value in having the task write this stuff when verbose is set, instead
of my script echoing these. I was hoping others would see value as well,
but if I am the only one...well I will make due.
Anyone else with an opinion?
Thanks,
Jason
-----Original Message-----
From: Tomas Restrepo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 27, 2002 8:07 PM
To: [EMAIL PROTECTED]
Subject: Re: [NAntC-Dev] Feature Request: Better verbose messages on the SQL
task
> Better verbose messages on the SQL task
> I would like to see better verbose messages when executing the SQL
> task.
>
> * Output of the actual sql statement being executed
Humm... what form would this take? I don't do it because I haven't found a
way to do it cleanly, particularly while batching commands.
> * Any results of the SQL statement
Results? You should get those if you add the print="true" attribute to the
task. Or are we talking about something different?
> * the connection string and/or connection settings.
In what form? I'm reluctant to print this info, since it is something you
could very easily do now just adding an extra <echo> task to your target...
--
Tomas Restrepo
[EMAIL PROTECTED]
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
_______________________________________________
NAntContrib-Developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
_______________________________________________
NAntContrib-Developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
