Hi Dr. Hipp,
Probably a low concern for you at 1:30am your time but I can't connect
to fossil-scm.org or sqlite.org over port 80.
$ curl http://sqlite.org/
curl: (7) Failed to connect to sqlite.org port 80: Connection refused
$ curl http://fossil-scm.org
curl: (7) Failed to connect to
On 10/28/16, Jens Alfke wrote:
> Do I need to worry about concurrent calls to custom functions (or virtual
> tables) that I register with SQLite? They’re associated with only a single
> connection, but with Serialized mode, that connection could be used from
> multiple
Do I need to worry about concurrent calls to custom functions (or virtual
tables) that I register with SQLite? They’re associated with only a single
connection, but with Serialized mode, that connection could be used from
multiple threads. And what if I use `pragma threads` to enable helper
On 10/28/2016 11:44 PM, John Reynolds wrote:
I've submitted a ticket,
https://system.data.sqlite.org/index.html/tktview?name=d4728aecb7, and want to
add a
comment to it. I can't find any obvious way to do it in the ticket page (I'm
logged on as
anonymous). Is it possible?
Click the "Edit"
I've submitted a ticket,
https://system.data.sqlite.org/index.html/tktview?name=d4728aecb7, and want to
add a
comment to it. I can't find any obvious way to do it in the ticket page (I'm
logged on as
anonymous). Is it possible?
-John
___
sqlite-users
Thank you,
I think you're right,
I did not see this in the documentation.
Thanks.
-Message d'origine-
De : sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] De la
part de Bernardo Sulzbach
Envoyé : vendredi 28 octobre 2016 17:49
À :
On 10/28/2016 09:53 PM, David Raymond wrote:
So my new understanding: This happens at the end of the write to the WAL file,
but before the actual checkpoint. And then any checkpoint just works normally.
So basically, even with journal_size_limit = 0, the WAL will always be at least
as large
On 10/28/2016 01:42 PM, cont...@comadd.fr wrote:
I think the value of 'match' should be FULL instead of NONE!
From the docs, "SQLite parses MATCH clauses (i.e. does not report a
syntax error if you specify one), but does not enforce them. All foreign
key constraints in SQLite are handled
Hello,
I use "SQLite for UWP" Release 3.15.0 for "Windows Store" developments.
I detected a strange thing on the SQLite database.
1. create two table :
CREATE TABLE artist (id INTEGER PRIMARY KEY, name TEXT);
CREATE TABLE track (id INTEGER PRIMARY KEY, name TEXT, artist_id INTEGER
REFERENCES
So my new understanding: This happens at the end of the write to the WAL file,
but before the actual checkpoint. And then any checkpoint just works normally.
So basically, even with journal_size_limit = 0, the WAL will always be at least
as large as the last write, even if checkpointed
SQLite version 3.14.0 2016-07-26 15:17:14
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> CREATE TABLE foo (bar INTEGER PRIMARY KEY AUTOINCREMENT);
sqlite> INSERT INTO foo (bar) VALUES(1234);
sqlite>
Works here;
SQLite version 3.13.0 2016-05-18 10:57:30
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> CREATE TABLE foo (bar INTEGER PRIMARY KEY AUTOINCREMENT);
sqlite> INSERT INTO foo (bar) VALUES(1234);
On 10/28/2016 05:39 PM, no...@null.net wrote:
Hi Rowan,
On Fri Oct 28, 2016 at 06:19:59PM +0800, Rowan Worth wrote:
Every sqlite_stmt you use *must* be finalized via sqlite3_finalize.
I'm not exactly sure what that looks like from the other side of DBD,
but I would be checking your perl code
Hi Rowan,
On Fri Oct 28, 2016 at 06:19:59PM +0800, Rowan Worth wrote:
>
> Every sqlite_stmt you use *must* be finalized via sqlite3_finalize.
> I'm not exactly sure what that looks like from the other side of DBD,
> but I would be checking your perl code for a statement/resultset
> object which
Hi Mark,
A quick google suggests this is a use after free error, as OpenBSD's
allocator apparently fills freed memory pages with the pattern 0xdfdfdfdfdf.
The stack trace reads like it is crashing while finalizing an sqlite_stmt,
as part of some automatic perl destructor logic.
Every
I am seeing a Bus Error at the end of a program that to my
inexperienced eye appears to have something to do with SQLite:
This GDB was configured as "amd64-unknown-openbsd6.0"...
Core was generated by `bif'.
Program terminated with signal 10, Bus error.
Loaded symbols for
Also if you have any connections open, the journal may exist, so it doesn't
have to constantly open and close it.
On Fri, Oct 28, 2016 at 2:21 AM, Dan Kennedy wrote:
> On 10/28/2016 03:16 AM, David Raymond wrote:
>
>> I'm playing around with WAL mode here for the first
On 10/28/2016 03:16 AM, David Raymond wrote:
I'm playing around with WAL mode here for the first time, along with some of
the pragmas, and I'm getting some weird results. I was hoping someone could let
me know if I'm missing something, or if yes, it is indeed weird.
For starters, I'm looking
After line:
UPDATE foo SET bar=5678;
put this sql command:
COMMIT;
If you execute all statements in one sql
(except last), they are executed in one transaction.
Regards
Radovan
Adam Goldman je 27.10.2016 ob 11:52 napisal:
Hi,
I expected the test case below to print 5679, but it prints 1235
19 matches
Mail list logo