RE: Forcing a sequence in a table
From: Victor Boris Arnold (anonymous_at_discussions.microsoft.com)
Date: 06/01/04
- Next message: Carlos Alvarez: "Company Name and Normalization"
- Previous message: Eric Butts [MSFT]: "RE: Database Corruption"
- In reply to: Jay Vinton: "RE: Forcing a sequence in a table"
- Next in thread: Dwayne Shrum: "RE: Forcing a sequence in a table"
- Reply: Dwayne Shrum: "RE: Forcing a sequence in a table"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Jun 2004 11:33:06 -0700
I don't think any of those suggestions will work for my
application. If row three was added last, but needs to be
listed before row two, none of these values will do the
trick.
>-----Original Message-----
>There is no point in worying about the physical
arrangement of data. Add a column that is timestamp,
autonumber, or some other scheme like max()+1 when
inserting new rows. Then use an Order By clause to sort
the result.
>.
>
- Next message: Carlos Alvarez: "Company Name and Normalization"
- Previous message: Eric Butts [MSFT]: "RE: Database Corruption"
- In reply to: Jay Vinton: "RE: Forcing a sequence in a table"
- Next in thread: Dwayne Shrum: "RE: Forcing a sequence in a table"
- Reply: Dwayne Shrum: "RE: Forcing a sequence in a table"
- Messages sorted by: [ date ] [ thread ]