On Mon, Jan 31, 2011 at 9:27 PM, Samuel Adam wrote:
> I can’t help you there other than to say, give your boss the facts and
> point out that if QA approved that schema, QA failed its job.
Would that it were it so easy. Unfortunately I work for a startup,
and this code was developed by a partne
t now (London). Will play around with settings
tomorrow...
On Mon, Jan 31, 2011 at 8:33 PM, Gabe da Silveira wrote:
> I'm working on a standalone test script to narrow down the problem...
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sq
On Mon, Jan 31, 2011 at 7:42 PM, Samuel Adam wrote:
> I suggested rewriting your schema. Non-TEXT data which will not be
> subjected to a MATCH search is best stored in another table and JOINed
> with the FTS3 table, as Mr. Hess also explained. Also, specifications
> such as VARCHAR(255) are no
On Mon, Jan 31, 2011 at 5:34 PM, Samuel Adam wrote:
> According to the docs, results from those queries should be reversed. I
> suspect that Mr. da Silveira’s different platforms actually have different
> SQLite versions, and that one version is consistent with the docs whereas
> the other is no
First of all, thank ou both Simon and Samuel for such thorough
consideration of this problem. I've been in meetings all afternoon
(London time) and will respond to each email where appropriate in
turn...
On Mon, Jan 31, 2011 at 1:24 PM, Samuel Adam wrote:
> On Mon, 31 Jan 2011 07:27:23 -0500, Si
he
fts documentation page (http://www.sqlite.org/fts3.html) indicates
column types are syntactic sugar, which seems relevant, but how can
the same script output a string in one case and an integer in another?
--
Gabe da Silveira
http://darwinweb.net
___
6 matches
Mail list logo
