Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

A bug in Sybase SQL Server ?

3 posts in Windows NT Last posting was on 1998-01-06 14:24:11.0Z
Stéphane MOREAU Posted on 1998-01-05 17:07:39.0Z
Message-ID: <34B1135B.425C59AE@apsydev.com>
Date: Mon, 05 Jan 1998 18:07:39 +0100
From: "Stéphane MOREAU" <stephm@apsydev.com>
Reply-To: stephm@apsydev.com
X-Mailer: Mozilla 4.04 [en] (WinNT; I)
MIME-Version: 1.0
Subject: A bug in Sybase SQL Server ?
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 27
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5318
Article PK: 1081398

With open client 10.0.4 (NT version) on a SQL Server 11.0 running under NT,
I've tried the following SQL statement :
SELECT User.name from sysobjects User
and then I get GPF on the server (no more SqlSrvr process on the server)

I agree that this statement is not very usefull but it appears in a different context in my
C/S application. In fact the problem appears as soon as you try to access in the select output field
a field User.*
If we try :
SELECT name from sysobjects User where User.name = 'foo'
there is an error in the parsing.

For my application this is not very important, since I've written a work around changing
User to User1. But it seems very strange to me that such a simple query issued by a
client side application like (WISQL) makes a GPF on the SERVER.

Could you please tell me if this is a known bug in the SQL server 11 and
if it disappears in version 11.5 or when it will be fixed

Thanks in advance,

Regards,

Stéphane MOREAU
Software engineer
AGDS - a suybsidiary of Peregrine System Inc.
FRANCE


BrunoMagal Posted on 1998-01-06 08:10:54.0Z
From: "BrunoMagal" <magal@sybase.com>
References: <34B1135B.425C59AE@apsydev.com>
Subject: Re: A bug in Sybase SQL Server ?
Date: Tue, 6 Jan 1998 09:10:54 +0100
Lines: 48
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Message-ID: <8fT#cInG9GA.62@forums.powersoft.com>
Newsgroups: sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5316
Article PK: 1081393

I agreee SQLServer reacts in a strange way to your request but ... "user" is
a reserved word of
transact-SQL. So you're not supposed to use it as a table name.
I tested with OC 10.0.4 and SQLServer 11.0.2.1 and got the normal error msg
: "Incorrect syntax near the keyword 'user' ". And I don't find any bug
about that.

Bruno Magal
Sybase Technical Engineer

Stéphane MOREAU wrote in message <34B1135B.425C59AE@apsydev.com>...
>With open client 10.0.4 (NT version) on a SQL Server 11.0 running under NT,
>I've tried the following SQL statement :
>SELECT User.name from sysobjects User
>and then I get GPF on the server (no more SqlSrvr process on the server)
>
>I agree that this statement is not very usefull but it appears in a
different context in my
>C/S application. In fact the problem appears as soon as you try to access
in the select output field
>a field User.*
>If we try :
>SELECT name from sysobjects User where User.name = 'foo'
>there is an error in the parsing.
>
>For my application this is not very important, since I've written a work
around changing
>User to User1. But it seems very strange to me that such a simple query
issued by a
>client side application like (WISQL) makes a GPF on the SERVER.
>
>Could you please tell me if this is a known bug in the SQL server 11 and
>if it disappears in version 11.5 or when it will be fixed
>
>Thanks in advance,
>
>Regards,
>
>Stéphane MOREAU
>Software engineer
>AGDS - a suybsidiary of Peregrine System Inc.
>FRANCE
>
>
>
>


BrunoMagal Posted on 1998-01-06 14:24:11.0Z
From: "BrunoMagal" <magal@sybase.com>
References: <34B1135B.425C59AE@apsydev.com> <8fT#cInG9GA.62@forums.powersoft.com>
Subject: Re: A bug in Sybase SQL Server ?
Date: Tue, 6 Jan 1998 15:24:11 +0100
Lines: 57
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Message-ID: <9JA2BZqG9GA.137@forums.powersoft.com>
Newsgroups: sybase.public.sqlserver.nt
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.sqlserver.nt:5315
Article PK: 1081392

You hit the bug 120462. The problem is fixed in SQLServer 11.0.3.

Bruno Magal
Sybase European Support Center

BrunoMagal wrote in message <8fT#cInG9GA.62@forums.powersoft.com>...
>I agreee SQLServer reacts in a strange way to your request but ... "user"
is
>a reserved word of
>transact-SQL. So you're not supposed to use it as a table name.
>I tested with OC 10.0.4 and SQLServer 11.0.2.1 and got the normal error msg
>: "Incorrect syntax near the keyword 'user' ". And I don't find any bug
>about that.
>
>Bruno Magal
>Sybase Technical Engineer
>
>Stéphane MOREAU wrote in message <34B1135B.425C59AE@apsydev.com>...
>>With open client 10.0.4 (NT version) on a SQL Server 11.0 running under
NT,
>>I've tried the following SQL statement :
>>SELECT User.name from sysobjects User
>>and then I get GPF on the server (no more SqlSrvr process on the server)
>>
>>I agree that this statement is not very usefull but it appears in a
>different context in my
>>C/S application. In fact the problem appears as soon as you try to access
>in the select output field
>>a field User.*
>>If we try :
>>SELECT name from sysobjects User where User.name = 'foo'
>>there is an error in the parsing.
>>
>>For my application this is not very important, since I've written a work
>around changing
>>User to User1. But it seems very strange to me that such a simple query
>issued by a
>>client side application like (WISQL) makes a GPF on the SERVER.
>>
>>Could you please tell me if this is a known bug in the SQL server 11 and
>>if it disappears in version 11.5 or when it will be fixed
>>
>>Thanks in advance,
>>
>>Regards,
>>
>>Stéphane MOREAU
>>Software engineer
>>AGDS - a suybsidiary of Peregrine System Inc.
>>FRANCE
>>
>>
>>
>>
>
>