Hi Jens,
the MATCH operator is not inside an OR expression. The MATCH operator is in an
AND expression, only the rowid request is in an OR expression.
Regards,
Hartwig
PS: In FTS5 since version 3.30.1 also the MATCH operator is allowed in OR
statements (try SELECT PlayersFTS.rowid FROM Players
On Jan 23, 2020, at 8:33 AM, Bernhard Rosenkraenzer wrote:
>
> The Debian guys have also observed this:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644
> (and also don't have a fix yet).
>
> Any ideas?
Can you bisect SQLite to narrow the range here? This release had an unusually
lo
On Jan 23, 2020, at 7:02 AM, Mark Benningfield wrote:
>
> ...whenever I do a Fossil pull of the latest
> version takes a grand total of about 2 seconds, but it would be nice not to
> have to remember to do it every time :)
If you’re having to reapply the change on every Fossil update, you’re pro
On Jan 23, 2020, at 5:45 AM, Dominique Devienne wrote:
>
> Hi. Looks like 3.31 (congrats on the release) does not include that
> small extension in the amalgamation. Could it please?
It’s easy to fix:
1. Get the SQLite source proper (https://sqlite.org/src/)
2. Add “uuid.c” to the loop curren
> On Jan 23, 2020, at 6:47 AM, mailing lists wrote:
>
> The following SELECT statement fails with the error "unable to use function
> MATCH in the requested context":
This is an annoying but documented limitation of FTS, not a bug. The MATCH
operator can’t be used inside an OR expression. It
On 1/23/20, Bernhard Rosenkraenzer wrote:
> Hi,
> after updating sqlite to 3.31.0, both firefox and thunderbird crash on
> startup (rebuilding them against the newer sqlite doesn't help).
Is this related to https://bugzilla.mozilla.org/show_bug.cgi?id=1607902
> Backtrace:
> (gdb) bt
> #0 0x
Hi,
after updating sqlite to 3.31.0, both firefox and thunderbird crash on startup
(rebuilding them against the newer sqlite doesn't help).
Backtrace:
(gdb) bt
#0 0x71b9fe20 in ?? () from /usr/lib64/firefox-71.0/libxul.so
#1 0x71b993d2 in ?? () from /usr/lib64/firefox-71.0/libxul
Hi,
create and fill the tables:
CREATE TABLE Games (ID INTEGER PRIMARY KEY, WhiteID INTEGER, BlackID INTEGER);
CREATE VIRTUAL TABLE PlayersFTS USING FTS5 (LastName,FirstNames);
INSERT INTO Games (WhiteID,BlackID) VALUES(1,2);
INSERT INTO PlayersFTS (rowid,LastName,FirstNames) VALUES(1,'A','1');
Well, I kinda thought that this would be fixed on the next release. The
"value_frombind" typo in particular prevents FTS3/4 from being built as a
loadable extension. I only have one legacy application that uses FTS3/4 that
way, and fixing these typos whenever I do a Fossil pull of the latest
versio
On 1/23/20, Ondrej Dubaj wrote:
> I discovered an issue found by coverity scan.
Thanks for the report. This was previously fixed here:
https://www.sqlite.org/src/info/465a15c5c2077011
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
Hi,
I discovered an issue found by coverity scan.
sqlite-src-326/shell.c:5697: var_compare_op: Comparing "zFree" to null
implies that "zFree" might be null.
sqlite-src-326/shell.c:5698: alias_transfer: Assigning: "zPath" =
"zFree".
sqlite-src-326/shell.c:5699: var_deref_model: Passing
Hi. Looks like 3.31 (congrats on the release) does not include that
small extension in the amalgamation. Could it please? Uuids are fairly
common in many schemas, so native support "by default" would
standardize support for them in the SQLite ecosystem. Thanks, --DD
PS: And we'd be able to retire
12 matches
Mail list logo