Re: Invalid cursor state

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 17:33:37 +0100

It is correct that the ANSI SQL standard parts from the relational model
regarding column ordering. Column are ordered in ANSI SQL (just look at an
INSERT statement without a column name list, or SELECT *).

Personally, I don't write production code which is dependent on column
ordering. I do agree with Erland's comments regarding "niceness" in database
diagrams, when you do ad-how queries and things like that. 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Martin Lingl" <martinlingl@chello.at> wrote in message
news:OoraAnqCEHA.2424@TK2MSFTNGP09.phx.gbl...
> In addition to Erland's comments (which I second), ANSI SQL-92 says the
> following about tables:
>     A table is a multiset of rows. A row is a nonempty sequence of
>     values. Every row of the same table has the same cardinality and
>     contains a value of every column of that table. The i-th value in
>     every row of a table is a value of the i-th column of that table.
>     The row is the smallest unit of data that can be inserted into a
>     table and deleted from a table.
>
> To me this clearly indicates that the columns of a table are ordered in
any
> ANSI SQL-92 compliant database, not just in SQL server, or else there
would
> not be an i-th value. I have read opposite opinions on this board many
> times.
>
> Martin
>
>
> "Aaron Bertrand [MVP]" <aaron@TRASHaspfaq.com> wrote in message
> news:%23%23suXPhCEHA.3132@TK2MSFTNGP11.phx.gbl...
> > Now, why does column order matter?  Or is this just a cosmetic thing?
> >
> > -- 
> > Aaron Bertrand
> > SQL Server MVP
> > http://www.aspfaq.com/
> >
> >
> > "Dean Slindee" <slindee@mindspring.com> wrote in message
> > news:OrLl8SgCEHA.464@TK2MSFTNGP11.phx.gbl...
> > > Thanks for your reply.
> > >
> > > After fiddling with it some more, the problem occurs when trying to
> insert
> > a
> > > column
> > > between other columns, but does not occur when appending the column at
> the
> > > end
> > > of the table.  I dealt with it by creating an empty table the way it
> > wanted
> > > it arranged,
> > > and inserting from the legacy table, and deleting the old table and
> > renaming
> > > the new table.  Problem bypassed.
> > >
> > > Dean Slindee
> > >
> > > "Erland Sommarskog" <sommar@algonet.se> wrote in message
> > > news:Xns94ACB21EEC540Yazorman@127.0.0.1...
> > > > Dean Slindee (slindee@mindspring.com) writes:
> > > > > I get the following message when attempting to insert a new column
> > into
> > > a
> > > > > table in design mode:
> > > > > - Unable to modify table.
> > > > > ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor
state
> > > > >
> > > > > Only SQL Server 2000 is connected to the database.
> > > > > What does this mean and how does one fix it?
> > > >
> > > > I say that this is a bug in Enterprise Manager. The user should
never
> > > > see any error like this.
> > > >
> > > > I have no idea what may have happened, but did you try to close down
> > > > EM, and start anew?
> > > >
> > > > Myself, and many other experience SQL professionals, prefer to use
> > > > SQL statements to change tables. Here is an example of the syntax
for
> > > > adding column to a table is:
> > > >
> > > >    ALTER TABLE tbl ADD col int NULL
> > > >
> > > >
> > > > -- 
> > > > Erland Sommarskog, SQL Server MVP, sommar@algonet.se
> > > >
> > > > Books Online for SQL Server SP3 at
> > > > http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
> > >
> > >
> >
> >
>
>

Relevant Pages