Error when table column name is "list" by Jacob Wagner

Closed

Type:	Bug
ID:	770637
Opened:	11/9/2012 11:32:28 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

SSMS generates an optomistic concurrency error when attempting to edit a row in a table where a column exists names "list".

Additional history at: http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/37a540bb-6ad8-4434-98eb-b15fad051460

Details (expand)

English

SQL Server 2008 R2 SP1

SQL Engine

Not Applicable

1) Create two tables:

CREATE TABLE dbo.Table1
(
    Name varchar(10)
    , [List] INT
    , timestamp
)
INSERT INTO dbo.Table1
Values( NULL, NULL, DEFAULT )
CREATE TABLE dbo.Table2
(
    Name varchar(10)
    , [Listt] INT
    , timestamp
)
INSERT INTO dbo.Table2
Values( NULL, NULL, DEFAULT )

2) Open each in SSMS using "Edit Top # Rows" option. Attempt to edit either column and you will discover that it works in Table2 but not in Table1.

An optomistic concurrency violation prevents updatign the row.

Row updates correctly.

0 attachments

Posted by Microsoft on 2/5/2013 at 4:24 PM

Hi! Jacob, thanks for writing in to Microsoft and reporting this bug.

We took a look at this bug and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this bug as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

Regards,
Sanjay Nagamangalam, SQL Server Manageability

Microsoft