On Wed, Jan 25, 2017 at 9:55 AM, Simon Slavin wrote:
>
> On 25 Jan 2017, at 5:45pm, Ersin Akinci wrote:
>
>> Thanks Richard and Simon for your insights. I think I'm still missing
>> a few things, though.
>>
>> 1. What does it mean when SQLite tries
On 25 Jan 2017, at 5:45pm, Ersin Akinci wrote:
> Thanks Richard and Simon for your insights. I think I'm still missing
> a few things, though.
>
> 1. What does it mean when SQLite tries to create an index on a string?
> Simon suggested that it's creating a calculated
Thanks Richard and Simon for your insights. I think I'm still missing
a few things, though.
1. What does it mean when SQLite tries to create an index on a string?
Simon suggested that it's creating a calculated index, but I'm not
sure what means. (Does it just mean an "index" literally just on
On 23 Jan 2017, at 9:33pm, Ersin Akinci wrote:
> CREATE INDEX index_reports_on_yearz_doesnt_exist ON reports
> (yearz_doesnt_exist);
> CREATE INDEX index_reports_on_yearz_doesnt_exist ON reports
> ('yearz_doesnt_exist');
> CREATE INDEX index_reports_on_yearz_doesnt_exist
On 1/23/17, Ersin Akinci wrote:
> CREATE INDEX index_reports_on_yearz_doesnt_exist ON reports
> ("yearz_doesnt_exist");
>
>
> I understand that the double quotation syntax is used to indicate
> identifiers. Why am I allowed to create an index on a non-existent column
>
I'm trying to track down a behavior in SQLite that I don't fully understand
and was hoping to get some help with. Here are three CREATE INDEX
statements for a table called reports that does NOT have a column called
yearz_doesnt_exist:
CREATE INDEX index_reports_on_yearz_doesnt_exist ON reports
6 matches
Mail list logo