Re: [sqlite] What is the C language standard to which sqlite conforms ?
On 24/11/62 06:18, Dennis Clarke wrote: On 11/23/19 4:46 PM, Dan Kennedy wrote: Some follow up and thank you all for looking at this. Using this mornings trunk/current/head I do see the tests running well with these little exceptions : boe13$ pwd /opt/bw/build/sqlite_20191121213415_rhel_74_3.10.0-693.el7.x86_64.006 ... build clean as usual :-) tests run nicely now until ... Can you run: ./testfixture test/journal3.test and post the output? It would be my pleasure to get some light tossed on this ... so here is a very clean compile ( no -std in CFLAGS at all on gcc 9.2.0 ) and the tests look like so : This is a test script error. Should now be fixed here: https://sqlite.org/src/info/b0b655625cf491c8 What version of Tcl are you using? Thanks, Dan. . . . Time: zipfile.test 442 ms Time: zipfile2.test 45 ms SQLite 2019-11-21 20:24:04 ac080432b480062507452d3cdbe6c0f759e6f95b65d9862e0462017405ab2b8e 8 errors out of 250191 tests on boe13.genunix.com Linux 64-bit little-endian !Failures on these tests: journal3-1.2.1.1 journal3-1.2.1.4 journal3-1.2.2.1 journal3-1.2.2.4 journal3-1.2.3.1 journal3-1.2.3.4 journal3-1.2.4.1 journal3-1.2.4.4 All memory allocations freed - no leaks Maximum memory usage: 9267192 bytes Current memory usage: 0 bytes Number of malloc() : -1 calls gmake: *** [Makefile:1252: tcltest] Error 1 real 420.72 user 383.25 sys 23.47 boe13$ boe13$ ./testfixture test/journal3.test journal3-1.1... Ok journal3-1.2.1.1... ! journal3-1.2.1.1 expected: [0o644] ! journal3-1.2.1.1 got: [00644] journal3-1.2.1.2... Ok journal3-1.2.1.3... Ok journal3-1.2.1.4... ! journal3-1.2.1.4 expected: [0o644] ! journal3-1.2.1.4 got: [00644] journal3-1.2.1.5... Ok journal3-1.2.2.1... ! journal3-1.2.2.1 expected: [0o666] ! journal3-1.2.2.1 got: [00666] journal3-1.2.2.2... Ok journal3-1.2.2.3... Ok journal3-1.2.2.4... ! journal3-1.2.2.4 expected: [0o666] ! journal3-1.2.2.4 got: [00666] journal3-1.2.2.5... Ok journal3-1.2.3.1... ! journal3-1.2.3.1 expected: [0o600] ! journal3-1.2.3.1 got: [00600] journal3-1.2.3.2... Ok journal3-1.2.3.3... Ok journal3-1.2.3.4... ! journal3-1.2.3.4 expected: [0o600] ! journal3-1.2.3.4 got: [00600] journal3-1.2.3.5... Ok journal3-1.2.4.1... ! journal3-1.2.4.1 expected: [0o755] ! journal3-1.2.4.1 got: [00755] journal3-1.2.4.2... Ok journal3-1.2.4.3... Ok journal3-1.2.4.4... ! journal3-1.2.4.4 expected: [0o755] ! journal3-1.2.4.4 got: [00755] journal3-1.2.4.5... Ok SQLite 2019-11-21 20:24:04 ac080432b480062507452d3cdbe6c0f759e6f95b65d9862e0462017405ab2b8e 8 errors out of 22 tests on boe13.genunix.com Linux 64-bit little-endian !Failures on these tests: journal3-1.2.1.1 journal3-1.2.1.4 journal3-1.2.2.1 journal3-1.2.2.4 journal3-1.2.3.1 journal3-1.2.3.4 journal3-1.2.4.1 journal3-1.2.4.4 All memory allocations freed - no leaks Memory used: now 0 max 260520 max-size 12 Allocation count: now 0 max 167 Page-cache used: now 0 max 0 max-size 1032 Page-cache overflow: now 0 max 2064 Maximum memory usage: 260520 bytes Current memory usage: 0 bytes Number of malloc() : -1 calls boe13$ Let me know if there is anything else I can try here. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Concurrency Question
On 24/11/62 00:05, Jens Alfke wrote: On Nov 23, 2019, at 7:17 AM, Dan Kennedy wrote: This should only happen if you are using shared-cache mode. Don't use shared-cache mode. Shared-cache mode also breaks Isolation between connections — during a transaction, other connections will see the writer’s intermediate state. (IIRC. It’s been a few years.) Only if you explicitly set "PRAGMA read_uncommitted" I think. Dan. In my experience, it’s only useful if all connections are read-only, or if you’re willing to use your own mutexes to keep writers from screwing up readers (in which case you might as well just share a single connection, right?) —Jens ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] Things you shouldn't assume when you store names
On Wed, 13 Nov 2019 15:37:15 -0600 Peter da Silva wrote: > My last name has a space in it. Don't get me started. My phone number has dashes in it, two to be exact. I don't remember the last website that accepted it verbatim. We're pretty far from a database discussion. It is a wonder, though, that Postel's Law is -- on the web built on the Internet he helped create -- observed amost entirely in the breach. --jkl ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
