Sylvain Leroux <[email protected]> writes: > Knut Anders Hatlen a écrit : >> [...] It is also possible to use optimizer overrides[2] to prevent >> the optimizer from using the index, in which case you'll get the rows >> in the order they are stored in the base table. > In that case, isn't there any chance that an INSERT will re-use the > space freed by a previous DELETE? Thus, the "file order" will no > longer be the "insert order".
That's correct, so adding some kind of orderable column and an ORDER BY clause is the only reliable way if getting them in the exact same order as they were inserted is an absolute requirement. -- Knut Anders
