Re: [sqlite] --disable-threadsafe broken in 3.25.x

On 01 Oct 2018, at 21:02, Fabrice Fontaine wrote: > Please find attached a patch fixing this issue. As this is my first > contibution to sqlite, please excuse me if I made any mistakes. Don't send attachment (not allowed), include it inline. -- Cheers -- Tim

[sqlite] --disable-threadsafe broken in 3.25.x

Dear all, Since commit https://github.com/mackyle/sqlite/commit/de41277e946d250b2d7331b6fe4addd22525d33 (and so since 3.25.x), --disable-threadsafe is broken in sqlite-autoconf. Indeed, the following line was removed: THREADSAFE_FLAGS=-DSQLITE_THREADSAFE=0 This line was setting the default

Re: [sqlite] DB To DB Transfer Time

> On Sep 25, 2018, at 11:14 AM, dmp wrote: > > The result for the 50K file db test of SQLite was 370.184 > seconds. Is this a reasonable transfer speed, given the > conditions noted? You haven’t specified how much of that time was spent in SQLite. For all we know, 370 seconds was spent in

Re: [sqlite] storing unsigned 64 bit values

> On Sep 27, 2018, at 3:53 AM, Conor Lennon wrote: > > The problem that I have is retrieving the value using c bindings. > I'm calling sqlite3_column_int64. > ... > When I call the function it returns back 9223372036854775807, which is the > maximum size of a signed 64 bit integer (one less

Re: [sqlite] read and write locking

Short version: The database will need to be in WAL mode https://www.sqlite.org/wal.html -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of p...@geniais.com Sent: Monday, October 01, 2018 9:57 AM To:

[sqlite] read and write locking

Hello, When I try to do a search from one script, returns not found when another script is writing, even though it is in another record. How can I make the script that are writing leave free to others for read only? Thank you Ismael ___

Re: [sqlite] .separator and .mode commands interactions

Luc Charansonney wrote: > sqlite> .separator tabs sqlite> select 1, 2; 1tabs2 > sqlite> .import mydata.txt mytable > Error: multi-character column separators not allowed for import You should have used ".separator \t". > So I fall back on my feet by using .mode instead of .separator: >

[sqlite] .separator and .mode commands interactions

Hello, I apologize if the question has already been asked before, but I need some clarification on the use of .mode and .separator relatively to the .import command. Say I have a structured tab-separated text file "mydata.txt" I want to import into a database using the .import FILE TABLE

Re: [sqlite] Issue altering table name

On 09/30/2018 06:59 PM, Luke Amery wrote: Hi sqliters, Is this a bug? sqlite> SELECT sqlite_version(); 3.25.1 sqlite> CREATE TABLE x(f1 integer NOT NULL PRIMARY KEY); sqlite> CREATE VIEW y AS SELECT f1 AS f1 FROM x; sqlite> CREATE TRIGGER t INSTEAD OF UPDATE OF f1 ON y BEGIN UPDATE x SET f1 =

Re: [sqlite] Calling sqlite3_create_module from a DLL

Deon Brewis wrote: > I have a DLL that makes a series of sqlite3_create_function_v2 calls. > It all works fine and the DLL is usable. > > I've tried adding a sqlite3_create_module into the same DLL, but I get > an assert in: > > sqlite3_mutex_try > over here: > assert(