On 7/04/2009 6:43 AM, Scott Baker wrote:
[snip]
> I must have typod and not noticed.
Your hypothesis carries within itself the seed of its own plausibility :-)
___
sqlite-users mailing list
sqlite-users@sqlite.org
Gerry Snyder wrote:
> Scott Baker wrote:
>> I didn't realize "INTEGER PRIMARY KEY" was case sensitive. Thanks
>
> Are you sure what you used before did not have a typo, or the words in a
> different order?
Good question... must have been. Testing it:
sqlite> CREATE TABLE foo (bar integer
On Mon, Apr 6, 2009 at 3:11 PM, Scott Baker wrote:
> Eric Minbiole wrote:
>>> If I have a query:
>>>
>>> SELECT foo FROM bar WHERE id = 14;
>>>
>>> How can I see if that query is optimized to use an index, and which index
>>> it's using. I thought if you did an EXPLAIN it
Scott Baker wrote:
> I didn't realize "INTEGER PRIMARY KEY" was case sensitive. Thanks
Are you sure what you used before did not have a typo, or the words in a
different order?
Gerry
___
sqlite-users mailing list
sqlite-users@sqlite.org
Eric Minbiole wrote:
>> If I have a query:
>>
>> SELECT foo FROM bar WHERE id = 14;
>>
>> How can I see if that query is optimized to use an index, and which index
>> it's using. I thought if you did an EXPLAIN it would show that, but I'm not
>> seeing it? Maybe it's not really using an index?
>
> If I have a query:
>
> SELECT foo FROM bar WHERE id = 14;
>
> How can I see if that query is optimized to use an index, and which index
> it's using. I thought if you did an EXPLAIN it would show that, but I'm not
> seeing it? Maybe it's not really using an index?
Use the command "EXPLAIN
If I have a query:
SELECT foo FROM bar WHERE id = 14;
How can I see if that query is optimized to use an index, and which index
it's using. I thought if you did an EXPLAIN it would show that, but I'm not
seeing it? Maybe it's not really using an index?
- Scott
7 matches
Mail list logo