July 27, 2011 at 4:29 am
Seriously?
Does Microsoft not have a clue how many people actually use the word "State" for table and column names? I mean, MS is based in the U.S. How could they not have realized that some people don't want to be using keywords in table names and column names? And now they've practically forced this upon us?
Could they not have named this keyword a little differently?
[/rant]
On a slightly less annoyed note, I can't even find it in BOL aside from "State Property", "State Enumeration", and "State Element". Does anyone know what this new keyword references or what other T-SQL construction this keyword is a part of?
July 27, 2011 at 5:21 am
This was removed by the editor as SPAM
July 27, 2011 at 5:40 am
stewartc-708166 (7/27/2011)
I found it in Reserved Keywords (Transact-SQL), Future Keywords section.
holly crap.. there's even more future keywords than the current ones :w00t:.
July 27, 2011 at 5:41 am
Thanks for the link. It explains why I can't figure out what State is being used for. So far, it's not.
July 27, 2011 at 4:53 pm
It's reserved to follow ANSI SQL-99 standard as a keyword.
-------------------------------------------------
Will C,
MCITP 2008 Database Admin, Developer
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply