Dynamic SQL generation for the UpdateCommand is not supported against a SelectCommand that does not return any key column information.

Question

0.00/5 (No votes)

See more:

C#

SqlCommand cd = new SqlCommand();
cd.CommandText = "select * from NONPRODUCTION_RESUME order by RESUMEID";
cd.Connection = con;
SqlDataAdapter da = new SqlDataAdapter(cd);
SqlCommandBuilder m_SQLCmdBuilder = new SqlCommandBuilder(da);
DataSet ds = new DataSet();
da.Fill(ds, "resid");
//ds.Tables["resid"].Constraints.Add("rid", ds.Tables["resid"].Columns["RESUMEID"], true);
int k = 1;
int var = 0;
        
for ( var = 0; var < ds.Tables["resid"].Rows.Count; var++)
{
  // DataRow dr=  
  ds.Tables["resid"].Rows[var]["RESUMEID"]=k;
  //dr.BeginEdit();
  //dr["RESUMEID"] = k;
  //dr.EndEdit();
  //dr.BeginEdit();
  //dr["RESUMEID"] = k;
  k++;
  //ds.Tables["resid"].GetChanges();
  da.Update(ds.Tables["resid"]);
  //ds.AcceptChanges();
}

I have the above code at where I am trying to rearrange the resume id after deleting middle rows.
But here I am getting an error like
Dynamic SQL generation for the UpdateCommand is not supported against a SelectCommand that does not return any key column information.

Posted 17-Feb-11 21:13pm

jagadeesh kumar adabala

Updated 17-Feb-11 21:15pm

JF2015

v2

Add a Solution

1 solution

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)

OriginalGriff · Answer 1 · 2011-02-17T21:36:00

Am I right in thinking that RESUMEID is the primary key for the table? And that it is an automatically incrementing integer?

If so, you can't change it. The database assigns them, the database maintains them. It will not let you change them.

Even if it would, it is a very bad idea to change a record ID at all. Consider this: you have two users, both execute your code at the same time. What ID is assigned? Are they all sequential?

No. Because one user has deleted record 14, and the other has deleted record 17. Neither knows about the other so they are both trying to give record 18 a different number. In fact, one of them has renumbered 17, so what the other deletes is actually record 18 anyway!

If you really need to use sequential numbering, then use the ordinal number of the record, rather than the ID: it is a lot safer, and does not need to be updated as it reflects the state of the database at that time.