one else should weigh in and the penny will finally
> drop if I am missing the point, but I'm still not seeing crawly things. :-)
>
>
> On 27 January 2017 at 10:01, Ersin Akinci wrote:
>
>> Michael,
>>
>> If I understood DRH and Simon correctly, I think the caus
Michael,
If I understood DRH and Simon correctly, I think the cause for concern
is that SQLite should be interpreting the single quotes as a string
literal, yet it interprets it as a column. Perhaps it's a strange
example (i.e., why would you want to index a string literal?), but
still, the behavi
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 to
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 the
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
(ye
5 matches
Mail list logo