Re: [sqlite] Re: does select reliably return insert order?
On 1/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > If you use LIMIT/OFFSET without an > explicit ORDER BY, you are relying on an implementation detail. Yes, but SQLite is an implementation. If it returns rows allways in the same order I don't see why it shouldn't be acknowledged - one mention in a documentation would make it a feature, and I think quite usefull one. If you write programs to rely on features that are not guaranteed then you, or the users, will be sorry later. You can learn from other people's mistakes or ignore their good advice. We can't force you to use common sense. -- -- The PixAddixImage Collector suite: http://groups-beta.google.com/group/pixaddix SqliteImporter and SqliteReplicator: Command line utilities for Sqlite http://www.reddawn.net/~jsprenkl/Sqlite Cthulhu Bucks! http://www.cthulhubucks.com
RE: [sqlite] Re: does select reliably return insert order?
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 21, 2007 2:40 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Re: does select reliably return insert order? > > > > If you use LIMIT/OFFSET without an > > explicit ORDER BY, you are relying on an implementation detail. > > Yes, but SQLite is an implementation. If it returns rows allways in the > same > order I don't see why it shouldn't be acknowledged - one mention in a > documentation would make it a feature, and I think quite usefull one. If the current implementation of SQLite returns rows always in the same order and is documented as such, then future versions of SQLite will be bound by that. While that may seem like a Good Thing for now, it will hamper future optimizations or changes to the pager, btree or other modules. By leaving it undocumented and not committing to today's implementation, DRH leaves himself open to change or optimize it later without breaking backward compatibility. Robert - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Re: does select reliably return insert order?
> If you use LIMIT/OFFSET without an > explicit ORDER BY, you are relying on an implementation detail. Yes, but SQLite is an implementation. If it returns rows allways in the same order I don't see why it shouldn't be acknowledged - one mention in a documentation would make it a feature, and I think quite usefull one. -- Nawet 50MB w jednym liscie>>> http://link.interia.pl/f19e7 - To unsubscribe, send email to [EMAIL PROTECTED] -
