Why not use a timestamp column to guarentee the order in which rows get inserted into the table? You can then order on the timestamp column. Gerhard Schmidt wrote: > > --d6Gm4EdcadzBjdND > Content-Type: text/plain; charset=iso-8859-1 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Hi,=20 > > I wounder why there is no support for Auto_increment fields in Heap > tables. I know there is a problem with the uniqueness of this columns=20 > but some times the uniqueness of the column is only needes as long=20 > as the heap table exists.=20 > > I=B4m currently working on system for Managing http Session and would like= > =20 > to use a heap table for storing the session information. Session=20 > information is only of temporary intrest. But still I need an unique=20 > ID for reference with some other Tabels storing dtaa for the session.=20 > All these tables are Heap tables. So there is no Probelem if the ID=20 > generated by the auto_increment column is not unique when the Database > server is restarted.=20 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
