Thanks for clearing that up
Greg
- Original Message -
From: D. Richard Hipp
To: [EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 11:52 AM
Subject: Re: [sqlite] Re: [inbox] Re: [sqlite] Primary key and index
Greg Obleshchuk wrote:
>
> So in these cases there is no
v t wrote:
> Hi
>
> When I execute the following query on a in-memory database, I get no results.
> The query is " SELECT * FROM SQLITE_TEMP_MASTER WHERE type='table'". I
^^
Should be "SQLITE_MASTER" not "SQLITE_TEMP_MASTER"
>
Greg Obleshchuk wrote:
So in these cases there is no benefit from creating an index on a column
that is INTEGER PRIMARY KEY?
Putting an index on an INTEGER PRIMARY KEY will make INSERT,
DELETE, and UPDATE slower since the index must be maintained.
But no SELECT will ever use the index. So
Hi Richard,
So in these cases there is no benefit from creating an index on a column that is
INTEGER PRIMARY KEY?
If so is there a way of exposing the fact that INTEGER PRIMARY KEY are used as the key
tot he B-Tree table? By looking in SQLite_Master it isn't obvious at all.
regards
Greg
Hi Everyone,
Does anyone know how to use hex values in an equation to be used in the select
statement?
Ex: If the select statement is
select (111 & 0x03FF)*5.0/1024
I get an error with this. It cannot understand 0x3FF. Without the hex, the select
statement works fine.
Thanks in advance
Hi,
Doing some testing , creating a primary key with the INTEGER defined will not create
an index but creating a PRIMARY KEY by it self does create an index
I.e
Create table z(a PRIMARY KEY, B);
creates an index
but
Create table z(a INTEGER PRIMARY KEY, B);
does not
So Yes I would be creating
Brass Tilde wrote:
My understanding is that SQLite has had this auto-update feature since
version 2.6.0. If I understand correctly, you should only have a problem if
you are *now* using a version prior to that, and go from that version
directly to 2.8.12 or later. If you've kept your version of
> On 6 Feb 2004, at 14:05, D. Richard Hipp wrote:
>
> > If you use a modern version of SQLite (version 2.6.0 through 2.8.11)
> > to open an older database file (version 2.1.0 through 2.5.6) the
> > library will automatically rebuild all the indices in the database
> > in order to correct a design
Tim Krah wrote:
Is this a bug?
Yes, it is a bug. It has been around for ages (since
version 2.4.0, 2002-March-11) but you are the first
to notice it.
See http://www.sqlite.org/cvstrac/tktview?tn=601
The bug has now been fixed.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
On 6 Feb 2004, at 14:05, D. Richard Hipp wrote:
If you use a modern version of SQLite (version 2.6.0 through 2.8.11)
to open an older database file (version 2.1.0 through 2.5.6) the
library will automatically rebuild all the indices in the database
in order to correct a design flaw in the older
You are right!
The developper tools on MacOSX have to be installed.
Franz
Am 09.02.2004 um 07:39 schrieb Will Leshner:
On Feb 8, 2004, at 10:04 PM, Franz Marty wrote:
Reason: Searching for a procedure to install sqlite on MacOSX. Does
the source code 2.8.12 need some preprocessing before
11 matches
Mail list logo
