FreeTDS Development Group

["Stephen Prowse" <stephen.prowse AT db.com>]

"Stephen Prowse" <stephen.prowse AT db.com> wrote:
> We have in the past written many shell scripts using sqsh , or isql, in 
> the form
> 
> sqsh -U -P -S << EOF | sed 's/{tab}$//'> file #where {tab} is the
> control character for tab
> select something 
> from somewhere
> whre things match.
> EOF
> 
> Process the results
> 
> Repeat the command with a different sql statement<<EOF2
> sql statement2
> EOF2
> ....
> 
> When trying with freetds , version 0.62.4 , with the same structure the 
> commands after the first EOF are ignored. We can get around this by 
> calling the sql in separate scripts from a parent but it adds to the 
> maintenance. Could anyone advise a way to get the above to work?

>>I think by "freetds" you mean tsql?  It would be interesting to get this
>>to work with tsql, but that really not its purpose.  It's just a testing
>>tool, not a general script processor. 

>>I'd be interested to hear how you fare with bsqldb. 

I have the same, actually worse issue, with bsqldb in that it doesn't 
return the rows with column separators and nor can I see how to do it 
without writing a perl program.

I'll struggle on with multiple scripts.

> I'd continue to use sqsh but from what I can see it won't work against 
> MSSQL.

>>You can use sqsh with Microsoft servers just fine.  I do, all the time. 
>>Does that solve the problem?   

I'll try that.

Regards

Steve