-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
with the recent replacement of awk build scripts with tclsh ones, a
problem has risen. The tcl is not commonly available when building the
environment/distribution from ground up (bootstrap), and as a
consequence, SQLite can no longer be built in
Using the example from the documentation at https://www.sqlite.org/fts5.html
I thought this worked in a previous version.
CREATE TABLE tbl(a INTEGER PRIMARY KEY, b, c);
CREATE VIRTUAL TABLE fts_idx USING fts5(b, c, content='tbl', content_rowid='a');
CREATE TRIGGER tbl_ai AFTER INSERT ON tbl BEGIN
James K. Lowden wrote:
> On Thu, 22 Oct 2015 15:23:38 +0200
> "Marco Turco" wrote:
>> The problem is when I link the generated library. I receive the
>> following error related to the first two warnings so I'm unable to
>> generate the executable file.
>
> You've solved the problem by compiling
On 10/27/15, Jan Stan?k wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
> with the recent replacement of awk build scripts with tclsh ones, a
> problem has risen. The tcl is not commonly available when building the
> environment/distribution from ground up (bootstrap), and as a
>
Hi there,
I experienced a SIGSEGV running the following code:
sqlite3* memory_db = NULL;
sqlite3_open("file::memory:?cache=shared", _db);
To be exact, it occurs when executed a second time. The whole function looks
like this
void init() {
sqlite3* memory_db = NULL;
On 10/27/15, Lohmann, Niels, Dr. (CQTN) wrote:
> Hi there,
>
> I experienced a SIGSEGV running the following code:
Can you provide us with a stack trace at the point of the crash?
>
> sqlite3* memory_db = NULL;
> sqlite3_open("file::memory:?cache=shared", _db);
>
> To be exact, it
This is on v3.9.1. I'm not sure exactly when it stopped working. I was using
the external content functionality with triggers to keep the virtual table
updated as part of a larger program, but found that the referenced example from
the docs exhibits the same issue. INSERT's work fine, but
Thanks for fixing it, Dan. Do you know when this will be rolled into an
official or preliminary autoconf file? Thanks again.
On Tue, 27 Oct 2015 12:24:03 +0100
Clemens Ladisch wrote:
> > You've solved the problem by compiling for a single-threaded
> > environment.
>
> No; the single-threaded environment is the problem.
That's a matter of opinion. Another way to look at it: threads set
back computing by 20 years.
9 matches
Mail list logo