FreeTDS Development Group

[Andrew Pimlott <andrew AT pimlott.net>]

On Thu, Jul 03, 2003 at 08:30:00AM +0200, Michael Peppler wrote:
> On Thu, 2003-07-03 at 02:21, Andrew Pimlott wrote:
> > I have a create trigger statement (that I didn't write) with a line
> > 
> >         declare @rc int;
> > 
> > When I run it with sqsh, I get
> > 
> >     Line 8: Incorrect syntax near 'int'.
> > 
> > (line 8 being that line).  If I erase the ';', it runs fine.  The
> > original code runs fine in a native MSSQL query tool.
> 
> Interesting - maybe the MSSQL query tool silently removes the
> semi-colon.

I doubt it's just that:  The line above is part of a long statement,
so the query tool would have to be parsing the whole statement.
Plus, I found other discrepancies (since sending the message), for
example with sqsh I get complaints of errors that the MSSQL tool
ignores, like non-existent columns (in this respect, sqsh works
better!).  Also, I had to change "GO" to "go" in one place.  It
really seems like I'm using a whole (but subtly) different mode.

> In any case the semi-colon shouldn't be there T-SQL doesn't use
> statement terminators like C or perl (and sqsh will often interpret the
> ; as meaning "go" - i.e. send the current SQL batch to the server).

You're right that removing the semicolon makes everyone happy.

Andrew