what is the main reason why we can't use inbuilt words as column name or sp?

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

, +

Hello ,

i have one small question i know solution but dont know why it happens

i was developing one project before i have named my column name as

SQL

get int allow null

now when i use stored procedure to insert update data in get then working very good but when i update my record directly from table like this

SQL

get buy 
 0   1
when i change this 0 to 1 there is error

error converting varchar value 'get' to datatype int

now when i change the get to gett it works fine but i dont know why we can not use system words of sql??
any suggestoins??

Posted 12-Aug-13 20:26pm

Dholakiya Ankit

Add a Solution

2 solutions

Solution 1

Strictly speaking its better not to use the keywords which has the inbuilt features or fuctions. Look for alternative words with similar meaning. But in rare case if you still want to go with the keywords then surround them usign sqare brackets '[]' for ex. in your case [get]. So that the parser understand it as a normal word rather than inbuild keyword.

Posted 12-Aug-13 20:33pm

ArunRajendra

Comments

Dholakiya Ankit 13-Aug-13 2:35am

ok but if i use as [get] then in sp also i have to use like
insert into [get] values 1 right?

ArunRajendra 13-Aug-13 2:43am

Yes some it also depends on the keyword. I tried this code in 2008 it works even for get and int. But it is always advisable to use []. I am not sure if there is settings which can be used to enable / disable this feature by admin.

<pre lang="sql">declare @t table
(
get int
)

declare @t1 table
(
int int
)

insert into @t(get) values (1)
insert into @t(int) values (1)</pre>

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Accepted Answer · 2013-08-12T21:01:00

Quote:
Microsoft SQL Server uses reserved keywords for defining, manipulating, and accessing databases. Reserved keywords are part of the grammar of the Transact-SQL language that is used by SQL Server to parse and understand Transact-SQL statements and batches. Although it is syntactically possible to use SQL Server reserved keywords as identifiers and object names in Transact-SQL scripts, you can do this only by using delimited identifiers.

Source: Reserved Keywords (Transact-SQL)[^]