loper to join our team building
products. Position is in the Washington D.C. metro area. If interested
contact [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 17, 2007 11:18 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Inse
> I know this is the behavior for MySQL, but not sure about SQLite.
I'v heard about some version of mysql that didn't return rows in the same
order (but haven't seen it myselt). So unless this behaviour is documented
in mysql manual, it's not a good idea to rely on this. Actually I'v seen
only
ested
contact [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 17, 2007 11:18 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Insert order maintained?
> I know this is the behavior for MySQL, but not sure about SQLite.
I'v
Additionally, note that if you use ORDER BY, and it _is_ in the
indicated order already, then sqlite will optimize the ORDER BY away
entirely. So use ORDER BY.
-scott
On 4/17/07, Andrew Finkenstadt <[EMAIL PROTECTED]> wrote:
The order of the rows returned by a select that does not have an ORD
The order of the rows returned by a select that does not have an ORDER BY
clause is guaranteed by the standard to be in any arbitrary order, even from
one execution to another due to changes in the underlying data, index
statistics, amount of memory available, or even the phase of the moon.
Use a
Hi
I would like to know if the order I get the rows from a select
(without ORDER BY) is the order by which the values were inserted.
I know this is the behavior for MySQL, but not sure about SQLite.
THank you
Alberto
--
Alberto Simões
---
6 matches
Mail list logo