Hi Ken, >Every sqlite table has an (hidden) index for its OID. When you create a >column as INTEGER PRIMARY KEY, the index for that column will simply be the >OID index. So creating another one is unnecessary.
Not that I disagree with you but where are you getting this information from? I just want to do some reading on it. regards Greg ----- Original Message ----- From: Williams, Ken To: 'Greg Obleshchuk' ; Michael Hunley ; [EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 7:47 AM Subject: RE: [sqlite] Re: [inbox] Re: [sqlite] Primary key and index > -----Original Message----- > From: Greg Obleshchuk [mailto:[EMAIL PROTECTED] > Sent: Monday, February 09, 2004 2:38 PM > To: Michael Hunley; [EMAIL PROTECTED] > Subject: [sqlite] Re: [inbox] Re: [sqlite] Primary key and index > > > 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'm not sure why you needed to run a test for that, it's just what the docs say. > So Yes I would be creating an index on the a column if it is > an autonumber(identity ) column if I was using this column in > joins or where clauses. No. Every sqlite table has an (hidden) index for its OID. When you create a column as INTEGER PRIMARY KEY, the index for that column will simply be the OID index. So creating another one is unnecessary. -Ken
