Re: ant sql query weirdness

2009-11-17 Thread Richard Brunelle
I added some targets and set onerror="continue": here is the complete code: SELECT * FROM accounts; SELECT * FROM us_states;

Re: ant sql query weirdness

2009-11-16 Thread glenn opdycke-hansen
What is the output from verbose? ant -v ... On Mon, Nov 16, 2009 at 08:29, Scot P. Floess wrote: > > I see you have onerror set to stop. What happens if you don't set that > attribute? It defaults to abort if not set... > >

Re: ant sql query weirdness

2009-11-16 Thread Scot P. Floess
I see you have onerror set to stop. What happens if you don't set that attribute? It defaults to abort if not set... On Sun, 15 Nov 2009, Richard Brunelle wrote: Yes, both echo statements get executed. Thanks Scot. On Sun, Nov 15, 2009 at 9:49 PM, Scot P. Floess wrote: Question for y

Re: ant sql query weirdness

2009-11-15 Thread Richard Brunelle
Yes, both echo statements get executed. Thanks Scot. On Sun, Nov 15, 2009 at 9:49 PM, Scot P. Floess wrote: > > Question for you...Do both echo statements get executed? Meaning, both > targets in the depends are honored (printUsStatesData -and" > printAccountsData's echo statements are execute

Re: ant sql query weirdness

2009-11-15 Thread Scot P. Floess
Question for you...Do both echo statements get executed? Meaning, both targets in the depends are honored (printUsStatesData -and" printAccountsData's echo statements are executed)... On Fri, 13 Nov 2009, Richard Brunelle wrote: This is driving me crazy I have the following code in an

ant sql query weirdness

2009-11-13 Thread Richard Brunelle
This is driving me crazy I have the following code in an ant file. SELECT * FROM accounts; SELECT * FROM us_states; individidualy, each of these targets return proper