As far as I know, DELETE's make gaps in the table (you could remove these by optimizing). If you INSERT into a table with gaps, your INSERTed row will try to fill the gaps created by that. Maybe it works backwards in filling the gaps?
-----Original Message----- From: Jeff McKeon [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 8:44 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Strange behavior on insert I understand how to use the "Order By" clause on a select, I'm trying to better understand why does this happen on the insert. Jeff > -----Original Message----- > From: Dan Wilterding [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 20, 2003 11:39 AM > To: [EMAIL PROTECTED] > Subject: Re: Strange behavior on insert > > > On 20 Nov 2003 at 11:12, Jeff McKeon wrote: > > > However when I go to the database and do a "select * from > tablename;" > > the records are in the table in the reverse order!! > > > > Even the auto increment is in reverse order... > > > > If you wish to retrieve the data in a particular order you must use > "order by" because the database itself does not depend on a > sequential > storage of the records. > > Dan Wilterding > [EMAIL PROTECTED] > > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?> [EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
