|
Home > Archive > MS SQL Server > March 2005 > letters 'go' removed from column names
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
letters 'go' removed from column names
|
|
| Usarian Skiff 2005-03-30, 9:40 am |
| I'm looking at an insert statement that someone else wrote, and I noticed
that every time the letters 'go" appear in a column name, he has removed
them (for instance a column named 'Category' appears in the insert statement
as 'Catery' and so on). I understand GO being an sql keyword, but I have
never had an issue with the server getting confused by GO being in a column
name. Is this just an old way of doing things? I think it's odd that his
SQL works fine this way.
Thanks!
| |
| Aaron [SQL Server MVP] 2005-03-30, 9:40 am |
| I doubt that the SQL "works fine" unless the tables have also had their
column names adjusted.
It sounds like someone got overly aggresive with search and replace, or else
the SQL you're viewing is being modified by your editor. Where are you
viewing these files? What type of files are they?
--
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"Usarian Skiff" <usarian. skiff@servicecenterm
etals.com> wrote in message
news:O3Gnt9TNFHA.3560@TK2MSFTNGP14.phx.gbl...
> I'm looking at an insert statement that someone else wrote, and I noticed
> that every time the letters 'go" appear in a column name, he has removed
> them (for instance a column named 'Category' appears in the insert
statement
> as 'Catery' and so on). I understand GO being an sql keyword, but I have
> never had an issue with the server getting confused by GO being in a
column
> name. Is this just an old way of doing things? I think it's odd that his
> SQL works fine this way.
>
> Thanks!
>
>
| |
| Narayana Vyas Kondreddi 2005-03-30, 9:40 am |
| An object name with the letters 'go' embedded init, should not cause a
problem. May be he just did a blind search and replace of 'go'.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/
"Usarian Skiff" <usarian. skiff@servicecenterm
etals.com> wrote in message
news:O3Gnt9TNFHA.3560@TK2MSFTNGP14.phx.gbl...
I'm looking at an insert statement that someone else wrote, and I noticed
that every time the letters 'go" appear in a column name, he has removed
them (for instance a column named 'Category' appears in the insert statement
as 'Catery' and so on). I understand GO being an sql keyword, but I have
never had an issue with the server getting confused by GO being in a column
name. Is this just an old way of doing things? I think it's odd that his
SQL works fine this way.
Thanks!
| |
| Kalen Delaney 2005-03-31, 7:01 am |
| GO is not a SQL keyword.
It is a command to the client tool like Query Analyzer to terminate the
batch. SQL Server attaches no special meaning to the word GO.
Like the others, my guess is that someone realized that SQL Server doesn't
like GO, so they just removed ALL of them from the file.
--
HTH
----------------
Kalen Delaney
SQL Server MVP
www. SolidQualityLearning
.com
"Usarian Skiff" <usarian. skiff@servicecenterm
etals.com> wrote in message
news:O3Gnt9TNFHA.3560@TK2MSFTNGP14.phx.gbl...
> I'm looking at an insert statement that someone else wrote, and I noticed
> that every time the letters 'go" appear in a column name, he has removed
> them (for instance a column named 'Category' appears in the insert
> statement
> as 'Catery' and so on). I understand GO being an sql keyword, but I have
> never had an issue with the server getting confused by GO being in a
> column
> name. Is this just an old way of doing things? I think it's odd that his
> SQL works fine this way.
>
> Thanks!
>
>
|
|
|
|
|