There's not enough information here to determine what the problem might be.
STOWED_EXCEPTION seems to be a microsoft crash dump artifact; I suspect
you'll need to somehow extract further exception details from that.
I'm not sure how to go about that exactly but here's some links to start
you off:
On 21/04/2017 1:43 AM, Dan Kennedy wrote:
Are you fossil-literate?
Primarily git literate (cvs years ago). Happy to work my way through it.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mail
Hello,
On 2017-04-19 19:31, Dan Kennedy wrote:
If you compile the code below with gcc 7.0.1:
gcc code.c -fsantitize=address -o tst
and then run:
./tst 2
Does the sanitizer make the same complaint?
[...]
/**/
[...]
switch( a ){
c
Here is the db https://ufile.io/q0314
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
you get back:
141| upload file漢_5
142| upload file漢_6
152| upload file漢_5
153| upload file漢_6
163| upload file漢_5
164| upload file漢_6
174| upload file漢_5
175| upload fil
On 2017/04/19 8:50 PM, Gabriele Lanaro wrote:
Dear SQLite communiy,
I’m trying to increase the performance of a query to its maximum possible
speed.
The schema is roughly constituted of two tables, one is a full text index,
fts5_table, while the other is called datatable.
The query in questio
On 04/20/2017 10:31 PM, Philip Warner wrote:
I've managed to get a version that runs down to API 9 by duplicating
some more classes from the Android sources and changing the cursor
window creation to use the old constructor with a boolean parameter
(rather than a name). Going below API 9 is pro
I've managed to get a version that runs down to API 9 by duplicating some more
classes from the Android sources and changing the cursor window creation to use
the old constructor with a boolean parameter (rather than a name). Going below
API 9 is probably going to involve diminishing returns in
On 04/20/2017 07:11 AM, Jonathan Gaillard wrote:
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
This certainly seems like a bug. Are you able to share the database that
exhibits the problem?
Thanks,
Dan.
you get back:
141| upload file漢_5
142|
On 2017-04-19 19:31, Dan Kennedy wrote:
On 04/18/2017 07:12 PM, Vitti wrote:
In my opinion this is probably due to erroneous usage of variable res
in the branches
of the huge switch in sqlite3VdbeExec
What's wrong with ``{ int res; res = 0; }''? The sanitizer should alert
in the following cod
On 19 Apr 2017, at 7:50pm, Gabriele Lanaro wrote:
> *SELECT* count(datatable.id) *FROM* fts5_table, datatable *WHERE*
> fts5_table *MATCH* ‘term’ *AND* datatable.id = fts5_column.rowid
If datatable.id is never NULL, then "count(*)" should do the same thing and be
faster.
> 1) ANALYZE
>
> Dec
If you do:
select rowid, name from filesfts where filesfts match '"upload
file漢_5"*';
you get back:
141| upload file漢_5
142| upload file漢_6
152| upload file漢_5
153| upload file漢_6
163| upload file漢_5
164| upload file漢_6
174| upload file漢_5
175| upload file漢_6
185| upload file漢_5
196| upload
Dear SQLite communiy,
I’m trying to increase the performance of a query to its maximum possible
speed.
The schema is roughly constituted of two tables, one is a full text index,
fts5_table, while the other is called datatable.
The query in question is a full text query on the full text index joi
Hello,
this is apparently not a bug. I have just read, that double quoted strings
are identifiers and no string literals...
(https://sqlite.org/lang_keywords.html)
Kindly Regards,
Andreas Martin
2017-04-19 13:46 GMT+02:00 Andreas Martin :
> Hello,
>
> I'll report a bug tested on SQLite 1.18.0,
Hello,
I'll report a bug tested on SQLite 1.18.0, Windows 7/64bit:
(You can reproduce this issue by using the attached SQL text file
"bug.sql").
The bug appears, when querying from a table with text compare, where a
column is named as like the text pattern:
SELECT * FROM tbl WHERE col_1="col_2";
Maybe Prakash Premkumar or Sairam Gaddam
, who seemed hell bent on implementing stored
procedures (or at least storing generated bytecode) about two years ago, have
made progress in the meantime?
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqli
Olivier Mascia wrote:
> As far as I understood, SQLite will parse and compile the trigger text
> as part of each statement using them. No bytecode compilation upfront,
> nor storage of it.
SQLite parses all triggers (and all other schema objects) when it reads
the schema (see "struct Trigger" and
16 matches
Mail list logo
