Re: [sqlite] sqlite-users Digest, Vol 147, Issue 13

Thank you, thank you! Balaji Ramanathan -- Forwarded message -- From: Richard Hipp To: General Discussion of SQLite Database < sqlite-users@mailinglists.sqlite.org> Cc: Bcc: Date: Thu, 12 Mar 2020 16:17:59 -0400 Subject: [sqlite] New SQLite Forum established - this mailing list is

Re: [sqlite] SQLite forum posts are about the forum, not SQLite

That should be. Also as stated in a previous email, I want to interact with the forum via email also. I mean, I have been using web forums for a long time and I find the UX _really,_ really lacking. GitHub allows me to comment on issues by email, which is more convenient for me. On Fri, Mar 13, 20

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On Wed, Mar 11, 2020 at 08:20:01AM -0400, Richard Hipp wrote: > On 3/11/20, Stefan Sperling wrote: > > > > Does this help? > > > > Studying the trace output makes me think this is the same problem that > came up on the s390 hardware and was fixed here: > https://www.sqlite.org/src/info/04885763c4

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On 3/11/20, Stefan Sperling wrote: > > Does this help? > Studying the trace output makes me think this is the same problem that came up on the s390 hardware and was fixed here: https://www.sqlite.org/src/info/04885763c4cd00cb Stefan: Can you verify that the patch above fixes the problem? If yo

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On 3/11/20, Stefan Sperling wrote: > > Does this help? > It does help some. But I need a good copy of the database schema, which I don't have. Please bring up the database file in the "sqlite3" command-line shell, then enter the command ".fullschema". Save off the results and send them to me,

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On Tue, Mar 10, 2020 at 06:42:18PM +0100, Stefan Sperling wrote: > On Tue, Mar 10, 2020 at 01:21:34PM -0400, Richard Hipp wrote: > > Set a breakpoint on the sqlite3VdbeExec() function that fires when the > > statement that is crashing is first executed. (You can determine that > > it is the correc

Re: [sqlite] Sqlite error code 14 when using 3.31.0+

Den 2020-03-10 kl. 12:31, skrev Daniel Polski: Den 2020-03-10 kl. 02:33, skrev Rowan Worth: On Mon, 9 Mar 2020 at 23:22, Daniel Polski wrote: Updated to 3.31.1 but my application started spitting out an error when opening the database, so I tested some earlier sqlite versions to figure ou

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

Stefan Sperling wrote: > > Does valgrind give any clues? > > Valgrind does not run on the OpenBSD/sparc64 platform, unfortunately. Would the address sanitizer (i.e. gcc -fsanitize=address, or clang -fsanitize=address) work on OpenBSD/sparc64? Regards Dominique ___

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On Tue, Mar 10, 2020 at 01:21:34PM -0400, Richard Hipp wrote: > On 3/10/20, Stefan Sperling wrote: > > The query being executed is "STMT_INSERT_NODE": > > -- STMT_INSERT_NODE > > INSERT OR REPLACE INTO nodes ( > > wc_id, local_relpath, op_depth, parent_relpath, repos_id, repos_path, > > revisi

Re: [sqlite] sqlite 3.31.1 crashes in SVN on OpenBSD/sparc64

On 3/10/20, Stefan Sperling wrote: > The query being executed is "STMT_INSERT_NODE": > -- STMT_INSERT_NODE > INSERT OR REPLACE INTO nodes ( > wc_id, local_relpath, op_depth, parent_relpath, repos_id, repos_path, > revision, presence, depth, kind, changed_revision, changed_date, > changed_aut

Re: [sqlite] Sqlite error code 14 when using 3.31.0+

Den 2020-03-10 kl. 02:33, skrev Rowan Worth: On Mon, 9 Mar 2020 at 23:22, Daniel Polski wrote: Updated to 3.31.1 but my application started spitting out an error when opening the database, so I tested some earlier sqlite versions to figure out when the problem starts. I don't get the message i

Re: [sqlite] Sqlite error code 14 when using 3.31.0+

Tuesday, March 10, 2020, 1:33:13 AM, Rowan Worth wrote: > On Mon, 9 Mar 2020 at 23:22, Daniel Polski wrote: >> Updated to 3.31.1 but my application started spitting out an error when >> opening the database, so I tested some earlier sqlite versions to figure >> out when the problem starts. >> I

Re: [sqlite] Sqlite error code 14 when using 3.31.0+

On Mon, 9 Mar 2020 at 23:22, Daniel Polski wrote: > Updated to 3.31.1 but my application started spitting out an error when > opening the database, so I tested some earlier sqlite versions to figure > out when the problem starts. > I don't get the message in versions <= 3.30.1. > > (from the appl

Re: [sqlite] sqlite-users Digest, Vol 146, Issue 27

On Thu, Feb 27, 2020 at 6:00 AM < sqlite-users-requ...@mailinglists.sqlite.org> wrote: > 18. Cannot export 'sqlite3' file to CSV (Rachael Courts) > From: Rachael Courts > To: "sqlite-users@mailinglists.sqlite.org" < > sqlite-users@mailinglists.sqlite.org> > Cc: > Bcc: > Date: Thu, 27 Feb 2020 0

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Dienstag, 28. Januar 2020 18:26:05 CET Brüns, Stefan wrote: > > On armv7l, there is another failure in the fuzztests, with and without the > patch: > sessionfuzz-data1.db: sessionfuzz: ./sqlite3.c:57249: pager_open_journal: > Assertion `rc!=SQLITE_OK || isOpen(pPager->jfd)' failed. I had previ

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Mittwoch, 29. Januar 2020 13:40:44 CET Richard Hipp wrote: > Please retry using this check-in: > https://www.sqlite.org/src/info/b20503aaf5b6595a The failings test now pass on all architectures: - ix86/x86_64 - armv7hl, aarch64 - ppc32be, ppc64be, ppc64le - s390x Kind regards, Stefan > On 1/

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

Please retry using this check-in: https://www.sqlite.org/src/info/b20503aaf5b6595a On 1/28/20, Brüns, Stefan wrote: > On Dienstag, 28. Januar 2020 18:26:05 CET Brüns, Stefan wrote: >> On Dienstag, 28. Januar 2020 16:16:01 CET Richard Hipp wrote: >> > On 1/27/20, Ondrej Dubaj wrote: >> > > Hi, >>

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Dienstag, 28. Januar 2020 18:26:05 CET Brüns, Stefan wrote: > On Dienstag, 28. Januar 2020 16:16:01 CET Richard Hipp wrote: > > On 1/27/20, Ondrej Dubaj wrote: > > > Hi, > > > > > > I came across a problem during mate test, where fuzzcheck ends with > > > segfault. > > > The problem appears to

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On Dienstag, 28. Januar 2020 16:16:01 CET Richard Hipp wrote: > On 1/27/20, Ondrej Dubaj wrote: > > Hi, > > > > I came across a problem during mate test, where fuzzcheck ends with > > segfault. > > The problem appears to be only on [s390x]. Other architectures are > > working fine. > > Fixed by

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On 1/27/20, Ondrej Dubaj wrote: > Hi, > > I came across a problem during mate test, where fuzzcheck ends with > segfault. > The problem appears to be only on [s390x]. Other architectures are > working fine. Fixed by check-in https://www.sqlite.org/src/info/04885763c4cd00cb Thanks for the tempora

Re: [sqlite] sqlite-3.31.0 segfaults on fuzzcheck on s390x architectures

On 1/27/20, Ondrej Dubaj wrote: > The problem appears to be only on this arches. That probably means it is an EBCDIC problem. We have no way of replicating or debugging this problem as we have no access to an s390 machine. Can RedHat perhaps provide one of the SQLite developers with a temporary

Re: [sqlite] Sqlite 3.31.0 breaks firefox and thunderbird

Thank you for the suggestion, Warren. Bisect first pointed to commit df51ae19c1aa4c26, but sometime after that this segfault seemed to be fixed, a second bisect blamed commit 2ae77bd233570834: https://www.sqlite.org/src/info/2ae77bd233570834 I've attached a backtrace from a crash at this commit

Re: [sqlite] Sqlite 3.31.0 breaks firefox and thunderbird

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

Re: [sqlite] Sqlite 3.31.0 breaks firefox and thunderbird

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

Re: [sqlite] SQLite 3.31.0 enters pre-release testing

Richard Hipp, on Friday, January 17, 2020 07:56 AM, wrote... > A terse summary of changes can be seen at > https://www.sqlite.org/draft/releaselog/current.html No gain in speed? :-) I love it when I see, "2% faster..." Thanks. josé ___ sqlite-users m

Re: [sqlite] SQLite command-line result is different from Perl DBI::Sqlite result (Keith Medcalf)

On 5 Jan 2020, at 5:01pm, Amer Neely wrote: > But the question still remains, why the different results? The optimizer gets improved from time to time in SQLite versions. SQLite solved the problem faster by breaking down your query differently: deciding whether to do one scan or use two index

Re: [sqlite] SQLite command-line result is different from Perl DBI::Sqlite result (Keith Medcalf)

> On Saturday, 4 January, 2020 18:31, Amer Neely > wrote: > >> I'm fairly new to SQLite, but have been using MySQL / mariadb in a local >> and web-based environment for several years. So far I'm happy and >> impressed with SQLite, but I recently noticed some odd behaviour with >> one of my querie

Re: [sqlite] SQLite command-line result is different from Perl DBI::Sqlite result (Igor Korot)

-- > What is your version of Perl and the SQLite module? This is perl 5, version 18, subversion 2 (v5.18.2) built for darwin-thread-multi-2level (with 2 registered patches, see perl -V for more detail) Copyright 1987-2013, Larry Wall SQLite version 3.30.1 2019-10-10 20:19:45 Enter ".help" for u

Re: [sqlite] SQLite command-line result is different from Perl DBI::Sqlite result

-- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. On Saturday, 4 January, 2020 18:31, Amer Neely wrote: >I'm fairly new to SQLite, but have been using MySQL / mariadb in a local >and web-based environment for several years

Re: [sqlite] SQLite command-line result is different from Perl DBI::Sqlite result

Hi, On Sat, Jan 4, 2020 at 7:31 PM Amer Neely wrote: > > Hello all, > I'm fairly new to SQLite, but have been using MySQL / mariadb in a local > and web-based environment for several years. So far I'm happy and > impressed with SQLite, but I recently noticed some odd behaviour with > one of my qu

Re: [sqlite] Sqlite database gets corrupted

On 20 Dec 2019, at 12:11pm, Syed Ahmad wrote: > Any way to recover it. This mailing list strips attachments. When's the last time you could use this file ? Did it have any form of encryption ? Was it usable with your own software ? Could you open it with the SQLite command-line tool ?

Re: [sqlite] sqlite sync over network

> On Dec 9, 2019, at 7:43 AM, George wrote: > > (litesync - SQLite Replication and Synchronization) > litesync seems to be a version of sqlite made by Ramos Bernardo from Brazil. Interesting, but I don't see how they can make those kinds of claims without running into conflicts on primary ke

Re: [sqlite] sqlite sync over network

thank you Jens,I have just found litesync (litesync - SQLite Replication and Synchronization) litesync seems to be a version of sqlite made by Ramos Bernardo from Brazil. | | | | litesync - SQLite Replication and Synchronization litesync makes easy to replicate and synchronize SQLite databa

Re: [sqlite] sqlite sync over network

> On Dec 5, 2019, at 8:05 AM, George wrote: > > Changes -> bidirectional. All terminals can save to db. Amount of collected > data it's not big and frequency between readings will be minimum 2sec. When > we push more readings. Data itself it's very small. Like reading temperature > from a pr

Re: [sqlite] sqlite sync over network

On 5 Dec 2019, at 4:48pm, George wrote: > We have an app already done in Qt on all terminals. Sqlite it's already used > by this app. When a terminal makes up a SQL INSERT command to add new data to the database, have it also save this command to a file. That's the file you send to the mast

Re: [sqlite] sqlite sync over network

On Thu, 2019-12-05 at 12:54 +, George wrote: > [EXTERNAL SOURCE] > > > > Hi, > I need to sync sqlite tables over network between few devices. > Please help me with an opinion with what will be the best approach ? > thanks, > George > ___ > sqlite-u

Re: [sqlite] sqlite sync over network

We have an app already done in Qt on all terminals. Sqlite it's already used by this app. The only missing part it's our sync to have data on PC for reports and also on screen reports on terminals if operator will need to check.We need sqlite because help us to manage data on terminal and displ

Re: [sqlite] sqlite sync over network

Okay. Do you really need all of the terminals to have up-to-date data from all the terminals ? If not, it's a simple problem: each terminal sends data to the master, which puts all the incoming data into the same database. Terminals don't need a SQL dataase at all. They simply report changes

Re: [sqlite] sqlite sync over network

Hi Simon, I miss to talk about sync trigger. Will be great to be after post trigger. I mean we read a probe on terminal T1, save data and on post trigger also put a job for sync and leave it on other thread to do this. If some sync jobs fail will must to try again to sync or on timeout  stay in

Re: [sqlite] sqlite sync over network

Hi Simon, Thx for helping me. I'm trying to explain our setup next: Changes -> bidirectional. All terminals can save to db. Amount of collected data it's not big and frequency between readings will be minimum 2sec. When we push more readings. Data itself it's very small. Like reading temperature

Re: [sqlite] sqlite sync over network

On 5 Dec 2019, at 12:54pm, George wrote: > I need to sync sqlite tables over network between few devices. > Please help me with an opinion with what will be the best approach ? Unfortunately this is a subject which has no simple solution. The things you have to do are not simple. To help us

Re: [sqlite] sqlite syntax auto suggest

Dear Richard & others, Now it is clear but how do I let the user make for example an UPDATE query without the OR. I have UPDATE on position 0, then I want OR, OF, tableName. This works but SET is only available on position 4-5. I want this also on position 2. What I want to do is get a li

Re: [sqlite] sqlite syntax auto suggest

Hello Dominique ! Here are two views that can bring that info to a query: == CREATE VIEW rule_list_view AS SELECT     a.ruleid,     b.name,     a.lhs FROM rule AS a LEFT JOIN symbol AS b ON a.lhs = b.id; CREATE VIEW rulerhs_list_view AS SELECT     a.ruleid,     b.name as symbol_name,     c

Re: [sqlite] sqlite syntax auto suggest

On Fri, Nov 29, 2019 at 2:10 PM Richard Hipp wrote: > On 11/29/19, Laurent wrote: > > > > Could you perhaps explain what pos means and what the [isTerminal] = > 0 rows mean. > > New check-in enhances the output to include a comment in the SQL > before the encoding of each production rule. This

Re: [sqlite] sqlite syntax auto suggest

On 11/29/19, Laurent wrote: > > Could you perhaps explain what pos means and what the [isTerminal] = 0 > rows mean. > New check-in enhances the output to include a comment in the SQL before the encoding of each production rule. This should help make it clear what the SQL is trying to represent.

Re: [sqlite] sqlite syntax auto suggest

Dear Richard, This has been very helpful, I have the parse.sql file. I feel very flattered that you took the time to answer my question. My boss says you are the one that should win a nobel prize. This has been much appreciated!! I completely understand if you won't answer anymore but I ca

Re: [sqlite] sqlite syntax auto suggest

Hello Richard ! Sorry by split my reply in so many small ones ! When trying to use the generate "parse.sql" I'm getting this: sqlite3 parse.db < parse.sql Error: near line 10: FOREIGN KEY constraint failed Error: near line 11: FOREIGN KEY constraint failed Error: near line 12: FOREIGN KEY

Re: [sqlite] sqlite syntax auto suggest

Hello Richard ! Again after rereading your reply and trying to use the "parse.sql" I noticed that it doesn't have a "begin;../commit;" wrapper as it's recommended to not having "fsync" calls on each insert. Cheers ! On 28/11/19 23:54, Richard Hipp wrote: On 11/28/19, Laurent Dhont wrote:

Re: [sqlite] sqlite syntax auto suggest

Hello Richard ! My bad after writing the last reply I found that "EXPLAIN" and "explain" are different symbols there. Could a small comment be generated at the begin of the generated "parse.sql" ? Something like: (dummy example) --- -- This is a generated output from lemon parse gen

Re: [sqlite] sqlite syntax auto suggest

Hello Richard ! I just looked at it and I have some doubts about the generated parse.sql, as I see it there is this table: CREATE TABLE symbol(   id INTEGER PRIMARY KEY,   name TEXT NOT NULL,   isTerminal BOOLEAN NOT NULL,   fallback INTEGER REFERENCES symbol ); --and this entries --..

Re: [sqlite] sqlite syntax auto suggest

On 11/28/19, Laurent Dhont wrote: > is there an API to > get this information in a format that is not an image? By coincidence, I checked in a change two days ago that might be helpful. See https://www.sqlite.org/src/timeline?c=4dbd398d640852d4 for the specific check-in. If you now build SQLite

Re: [sqlite] SQLite Message Passing Interface

On 26 Nov 2019, at 10:54pm, Enzo Madda wrote: > Id appreciate constructive feedback or questions, thanks! Your project is a feeder library to a SQL engine. So you might want to add to your documentation something about how your users can avoid SQL injection vulnerabilities. Or how your libra

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

On 8/11/62 00:15, Dennis Clarke wrote: On 2019-11-07 11:44, Shawn Wagner wrote: ... Just don't use strict c99 mode when compiling with gcc? Drop the -std argument from your CFLAGS to use the default (gnu11 since gcc 5) or explicitly use gnu99, which gives you that version of the C standard +

Re: [sqlite] SQLite with branching

On 4 Nov 2019, at 22:25, Jens Alfke wrote: >> On Nov 4, 2019, at 4:57 AM, Simon Slavin wrote: >> >> That's one of the reasons that the source code for SQLite is public: so that >> people can add the features they want. > > Totally agree. However, when you go off the mainline of SQLite you lose s

Re: [sqlite] SQLite with branching

I included WAL mode and mmap on the LiteTree simple benchmark. It turns out that WAL mode is as fast as LiteTree on Linux (with a hard disk) for writes and a little slower on reads. On MacBook Pro (with SSD) LiteTree is faster on both writing and reading. SQLite's mmap make it slightly fas

Re: [sqlite] SQLite with branching

> On Nov 7, 2019, at 9:02 AM, Bernardo Ramos wrote: > > If you are interested in just the performance without the branching feature, > there are at least 3 options: > > 1. SQLigthning: I was thinking in updating it to the last version of SQLite That would be awesome! I have looked at it a fe

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

Another option (Which the devs might consider) is to replace use of the asm keyword with __asm__, which is a form of the extension understood even in strict mode. (I have no idea why gcc doesn't offer intrinsics for bit rotation, as it's a common task and shouldn't require hacks like this to relia

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

On 2019-11-07 11:44, Shawn Wagner wrote: ... Just don't use strict c99 mode when compiling with gcc? Drop the -std argument from your CFLAGS to use the default (gnu11 since gcc 5) or explicitly use gnu99, which gives you that version of the C standard + gcc extensions. (Not that they have anythi

Re: [sqlite] SQLite with branching

Hi! I am the creator of LiteTree (also LiteReplica, LiteSync and 3 new products that will be released soon). When I was planning to add branching I discovered many ways to implement it. I selected the one that satisfied performance over disk usage. It can also be implemented the other way ar

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

... Just don't use strict c99 mode when compiling with gcc? Drop the -std argument from your CFLAGS to use the default (gnu11 since gcc 5) or explicitly use gnu99, which gives you that version of the C standard + gcc extensions. (Not that they have anything to do with the problem, but compiling wi

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

On 2019-11-07 11:15, Shawn Wagner wrote: Does that toolchain use gcc, or a different compiler? If gcc, are you using the same CFLAGS as on the redhat box (you're turning on a bunch of extra non-default options there)? I don't see how --with-threads can be a concern. The other options do not qu

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

For that matter, is the Solaris box x86 or sparc? If the latter, this particular code path obviously wouldn't ever be used on it. On Thu, Nov 7, 2019, 8:10 AM Dennis Clarke wrote: > On 2019-11-07 11:01, Shawn Wagner wrote: > > Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disa

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

Does that toolchain use gcc, or a different compiler? If gcc, are you using the same CFLAGS as on the redhat box (you're turning on a bunch of extra non-default options there)? On Thu, Nov 7, 2019, 8:10 AM Dennis Clarke wrote: > On 2019-11-07 11:01, Shawn Wagner wrote: > > Compiling with -std=is

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

On 2019-11-07 11:01, Shawn Wagner wrote: Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disables gcc extensions like inline asm. OKay but I have no issues doing a compile on a Solaris server using the Oracle Studio 12.6 tools and strict C99. So how is C99 the issue? Dennis

Re: [sqlite] sqlite-src-3300100 on RHEL 7.4 toss mad errors about 'asm'

Compiling with -std=iso9899:1999 is the culprit. Strict c99 mode disables gcc extensions like inline asm. On Thu, Nov 7, 2019, 7:57 AM Dennis Clarke wrote: > > While building sqlite from the zip file sqlite-src-3300100.zip I saw > what seems to be a normal configure and then madness : > > > boe1

Re: [sqlite] SQLite with branching

> On Nov 5, 2019, at 1:27 AM, Dominique Devienne wrote: > > AFAIK, that was one of the goals of SQLite4 [1], to change the backend to LSM. LMDB (LiteTree's back-end) doesn't use LSM; it's a B-tree manager. The speedup appears to come from a combination of techniques like eliminating caching

Re: [sqlite] SQLite with branching

On Tue, Nov 5, 2019 at 10:01 AM Wout Mertens wrote: > On Mon, Nov 4, 2019 at 10:26 PM Jens Alfke wrote: > > > I don't have a practical use for the branching features, though they're > cool, but I'm salivating at the thought of a 2x speedup. > > With all the work that's put into eking out small p

Re: [sqlite] SQLite with branching

On Mon, Nov 4, 2019 at 10:26 PM Jens Alfke wrote: > I don't have a practical use for the branching features, though they're cool, > but I'm salivating at the thought of a 2x speedup. > With all the work that's put into eking out small performance increases in > SQLite, I'd imagine the devs woul

Re: [sqlite] SQLite with branching

> On Nov 4, 2019, at 4:57 AM, Simon Slavin wrote: > > That's one of the reasons that the source code for SQLite is public: so that > people can add the features they want. Totally agree. However, when you go off the mainline of SQLite you lose some things, like easy updating to new SQLite re

Re: [sqlite] SQLite with branching

The post you quoted points to exactly that: a version of SQLite that handles branches. Check it out. That's one of the reasons that the source code for SQLite is public: so that people can add the features they want. ___ sqlite-users mailing list sqli

Re: [sqlite] SQLite with branching

@SQLite Guys: Do you have something like branching on your roadmap? I really like this feature and see a lot of use-cases beside the blockchain topic. And, of course if this works with your encryption extension that would be awesome. * simple versioning of a database: Useful when you want to kee

Re: [sqlite] [sqlite-dev] Error 25: column index out of range when binding for a DATETIME

On Thu, Oct 31, 2019 at 9:52 AM Keith Medcalf wrote: > On Thursday, 31 October, 2019 07:17, Jeffrey Walton > wrote: > ... > >/* negative for days in the past */ > >int days = 120; > >days = -days; > > >const char DELETE_STMT[] = "DELETE from blacklist " \ > >"WHERE dtime

Re: [sqlite] [sqlite-dev] Error 25: column index out of range when binding for a DATETIME

On Thursday, 31 October, 2019 07:17, Jeffrey Walton wrote: First, your question should go to the sqlite-users mailing list, not the developers mailing list. >I'm having trouble binding a parameter for a DELETE. I am trying to >delete records older than 120 days. Below, I have a table with a >c

Re: [sqlite] sqlite - AIX memory fault coredupm when using .output command [WARNING! - EXTERNAL]

On Oct 29, 2019, at 2:56 PM, Dawson, Jeff G wrote: > > SQLite version 3.7.14.1 2012-10-04 19:37:12 I infer that you’re migrating a legacy system. There are two good alternatives to your current method that should avoid the symptom entirely: 1. Build a current version of SQLite for the old AIX

Re: [sqlite] sqlite segfault bug report

On 28 Oct 2019, at 11:07am, Richard Hipp wrote: > Bisect: Just to explain to the Korean students: you spotted a real bug, but very recently the bug was fixed. However, your work is useful. Please download the current version of SQLite from and continue fu

Re: [sqlite] sqlite segfault bug report

On 10/28/19, Graham Holden wrote: > Monday, October 28, 2019, 5:46:55 AM, ??? wrote: > >> Code: > >> BEGIN; >> CREATE TABLE t1(a); >> ALTER TABLE t1 ADD c CHECK (b>c); >> PRAGMA writable_schema=on; >> INSERT INTO t1 VALUES(2,3); > >> Version: 3.29.0, 3.22.0 > > On "SQLite version 3.30.1 2019-10-1

Re: [sqlite] sqlite segfault bug report

Monday, October 28, 2019, 5:46:55 AM, ??? wrote: > Code: > BEGIN; > CREATE TABLE t1(a); > ALTER TABLE t1 ADD c CHECK (b>c); > PRAGMA writable_schema=on; > INSERT INTO t1 VALUES(2,3); > Version: 3.29.0, 3.22.0 On "SQLite version 3.30.1 2019-10-10 20:19:45" this returns an error after the thir

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

Roman Fleysher, on Thursday, October 10, 2019 04:31 PM, wrote... > Imagine a vehicle which has wheels to drive on a road. And wings to fly and > a hull to float. How nice and happy world would be !? True? Of course true. > > But, this vehicle would be bad as a car, bad as an airplane and bad a bo

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

On Oct 10, 2019, at 2:03 PM, Jose Isaias Cabrera wrote: > > 2. The normal SQlite snapshots plus a series of libraries and functions that > can easily be compiled with the original light SQLite. This is basically the model for FOSS OS distros: a bunch of people get together and work on a cohere

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

It's ok that you don't believe in it, but the last statement, you know is not true. I have been in this list since 2003 or so, and constantly there is one or two request to Dr. Hipp and the owners, per month, to add "stuff" to it. Or, things like, "I would love to have SQLite do...", etc. Fir

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

Roman Fleysher, on Thursday, October 10, 2019 04:17 PM, wrote... > > With your brain excluded, who is "we"? > > The beauty of SQLite is that SQL was distilled to the smallest and most > reproducible > on many platforms set. Over time, I see how developers expand functionality > to make it > more

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

> It has LEFT JOIN and does not have RIGHT JOIN. Why? Because RIGHT can be made > out of LEFT by swapping order of tables. The paradigma of SQL is to let the user describe what he wants to do, not to think about how to describe the problem so that the database system does understand. The lack o

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

Simon Slavin, on Thursday, October 10, 2019 04:12 PM, wrote... > > On 10 Oct 2019, at 9:03pm, Jose Isaias Cabrera, on > > > 2. The normal SQlite snapshots plus a series of libraries and functions that > can easily be compiled with the original light SQLite. > > Here's the simple way to start the p

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

With your brain excluded, who is "we"? The beauty of SQLite is that SQL was distilled to the smallest and most reproducible on many platforms set. Over time, I see how developers expand functionality to make it more convenient while maintaining reproducibility across platforms. Time, date, math

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

On 10 Oct 2019, at 9:03pm, Jose Isaias Cabrera wrote: > 2. The normal SQlite snapshots plus a series of libraries and functions that > can easily be compiled with the original light SQLite. Here's the simple way to start the project without breaking anything. Believers in SQLHeavy (or whatever

Re: [sqlite] SQLite plus the works (was Re: Opposite of SQLite)

It would be very useful (for me anyway :-) if SQLite followed the Postgres way of being able to install extensions - so for things like Spatialite it would be more embedded than stuck on the side... Retain the core "lite" DBMS but better facilitate being able to expand the functionality. Brent

Re: [sqlite] sqlite database changes not committed immediately

Error there when database is Local system as well as in a remote Filesystem. On Thu, Oct 3, 2019 at 4:14 PM Keith Medcalf wrote: > > Those examples appear to be using a database resident on a remote > filesystem. Is the database located on a remote filesystem? > > -- > The fact that there's a

Re: [sqlite] sqlite database changes not committed immediately

Those examples appear to be using a database resident on a remote filesystem. Is the database located on a remote filesystem? -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Thank you for the recommendations and latest adjustment, both work to resolve the issue. On Fri, Sep 27, 2019 at 12:37 PM Richard Hipp wrote: > On 9/27/19, Micah Moore wrote: > > Hello, > > > > Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation > in > > a [Catalyst]( > > h

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

On 9/27/19, Micah Moore wrote: > Hello, > > Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation in > a [Catalyst]( > https://developer.apple.com/ipad-apps-for-mac/) based project -- targeting > UIKit for macOS -- fails with the error "'gethostuuid' is unavailable: not > availa

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Hello, Attempting to use the Pre-release snapshot of SQLite 3.30.0 amalgamation in a [Catalyst]( https://developer.apple.com/ipad-apps-for-mac/) based project -- targeting UIKit for macOS -- fails with the error "'gethostuuid' is unavailable: not available on macCatalyst" Adapting this conditiona

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

On 9/26/19, Raitses, Alex wrote: > Hello, > I have noticed that security CVE > (https://nvd.nist.gov/vuln/detail/CVE-2019-16168) has been submitted on > SQLite. As far as I can see the patch was submitted to the trunk. > Will CVE patch be included in the 3.30.0? Yes. https://www.sqlite.org/src/t

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Hello, I have noticed that security CVE (https://nvd.nist.gov/vuln/detail/CVE-2019-16168) has been submitted on SQLite. As far as I can see the patch was submitted to the trunk. Will CVE patch be included in the 3.30.0? Regards, Alex -Original Message- From: sqlite-users On Behalf Of

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

"Still says" due to 3_30_0.html is in a draft, I would assume. On Thu, Sep 26, 2019 at 3:31 PM Olivier Mascia wrote: > > Le 26 sept. 2019 à 20:26, Richard Hipp a écrit : > > > > Our plan is to release SQLite version 3.30.0 in about two weeks - on > > or about 2019-10-10. Please review the chan

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

> Le 26 sept. 2019 à 20:26, Richard Hipp a écrit : > > Our plan is to release SQLite version 3.30.0 in about two weeks - on > or about 2019-10-10. Please review the change log > >https://www.sqlite.org/draft/releaselog/3_30_0.html > > And perhaps download, build, and test the latest snapsh

Re: [sqlite] SQLite version 3.30.0 in about two weeks.

Looks good. One request that popped to mind while looking at this: Would you expand the documentation on the index_info and index_xinfo pragmas to include what they return when run on an expression index? -Original Message- From: sqlite-users On Behalf Of Richard Hipp Sent: Thursday,

Re: [sqlite] SQLite - macOS

> On Sep 23, 2019, at 9:53 AM, Pierre Clouthier > wrote: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") That isn't necessary. SQLite defaults to UTF-8. In most cases SQLite doesn't interpret the byte sequences in a string. It just knows it's using an 8-bit character set and leaves it a

Re: [sqlite] SQLite - macOS

> On Sep 23, 2019, at 1:25 PM, Simon Slavin wrote: > >> On 23 Sep 2019, at 5:53pm, Pierre Clouthier >> wrote: >> >> Can anyone explain how to write UTF-8 in SQLite on the Mac? >> >> We use this statement: >> >> sqlite3_exec("PRAGMA encoding = \"UTF-8\";") > > This is not a SQLite problem

Re: [sqlite] SQLite - macOS

Hi, On Mon, Sep 23, 2019 at 11:58 AM Pierre Clouthier wrote: > > Can anyone explain how to write UTF-8 in SQLite on the Mac? > > We use this statement: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") You should probably use this inside #ifdef _WINDOWS #endif Thank you. > > This work

Re: [sqlite] SQLite - macOS

On 23 Sep 2019, at 5:53pm, Pierre Clouthier wrote: > Can anyone explain how to write UTF-8 in SQLite on the Mac? > > We use this statement: > > sqlite3_exec("PRAGMA encoding = \"UTF-8\";") This is not a SQLite problem, but a problem with escaping the quotes in language you're using to exe

  1   2   3   4   5   6   7   8   9   10   >