--- Brett Keating <[EMAIL PROTECTED]> wrote:
> Actually this wasn't the issue after all... Indices have nothing to do
> with it.
>
> The genre was being inserted from two different sources. It is a UTF-16
> string, and in one case it was being inserted with a null terminator,
> and in another
insert a value as "POP" and another value as
"POP0."
So in a sense this was merely user error but also an interesting
idiosyncracy of the sqlite3 database.
Thanks,
Brett
-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 11
--- Brett Keating <[EMAIL PROTECTED]> wrote:
> Msica independiente|text|19|0056_People Get Ready1_test1.wma
> POP|text|3|0057_The Mighty Ship1_test1.wma
> POP|text|3|0058_The Mighty Quinn1_test1.wma
>
> Anyway, it turns out the problem was caused by creating an index on the
> genre field. If I
. If I don't create an index, it works normally for both
OSes.
Thanks,
Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 22, 2007 9:07 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] bizarre query problem
Joe Wilson <[EMAIL PROTEC
Joe Wilson <[EMAIL PROTECTED]> wrote:
> Just for kicks, what happens on both platforms when you issue:
>
> select genre, length(genre), hex(genre), filename
> from objects where media_type=1;
>
Make that:
select genre, typeof(genre), length(genre), hex(genre), filename
from objects
Just for kicks, what happens on both platforms when you issue:
select genre, length(genre), hex(genre), filename
from objects where media_type=1;
as well as:
select count(*) from objects where genre LIKE '%POP%';
> I have a bizarre problem. Here is an example of something I tried in
>
Nothing you've mentioned is out of the ordinary. I would expect the
same behavior on both platforms.
Can you post the complete schema, and the exact query that exhibits the
problem? (And perhaps a couple of insert statements into the objects table).
Without this I don't think anyone can recreate
7 matches
Mail list logo
