Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent events occurring on or after 2020-11-10 04:51:36.
2020-11-12
| ||
22:31 | • Reply: OLE error 800A03EC when sending to Excel artifact: 59dc6ec839 user: kmedcalf | |
22:22 | • Reply: General question concerning database stucture and number of databases to use. artifact: 33b66d560b user: kmedcalf | |
20:12 | • Post: OLE error 800A03EC when sending to Excel artifact: 87da5dec9d user: anonymous | |
18:38 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: cc5c59cf79 user: kmedcalf | |
18:33 | • Reply: Help to solve database locked artifact: 10f1290a35 user: riguzlee | |
18:30 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: e40e0bc268 user: emmenlau | |
18:24 | • Reply: Help to solve database locked artifact: 5333a6ff12 user: kmedcalf | |
18:18 | • Reply: Help to solve database locked artifact: f80b7f9300 user: kmedcalf | |
17:06 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: 5b6cf729a2 user: Clothears | |
15:50 | • Post: Benchmarking SQLite versions against each other artifact: e542545a47 user: danshearer | |
15:40 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: 7011a93b75 user: emmenlau | |
15:34 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: 755230f9cb user: emmenlau | |
15:29 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: 014dd96863 user: LarryBrasfield | |
15:15 | • Reply: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: edae3aba69 user: drh | |
14:56 | • Post: Why Sqlite parse error: line 1:94: expecting RPAREN, found 'OR' in CHECK constraint? artifact: 4eec537d1a user: emmenlau | |
09:02 | • Post: Help to solve database locked artifact: 7bd85b9ab2 user: riguzlee | |
08:38 | • Reply: WAL journal file-size keeps on growing... artifact: 54e791a519 user: JohnSmith | |
08:05 | • Reply: Document or specify what json_extract does with nonexistant keys? artifact: d23ebcd6b1 user: EternityForest | |
06:36 | • Reply: Undetected table artifact: c16c641194 user: kmedcalf | |
06:18 | • Reply: General question concerning database stucture and number of databases to use. artifact: 3e70565463 user: 1codedebugger | |
05:30 | • Post: Undetected table artifact: d52697ce5c user: prkundan | |
2020-11-11
| ||
23:48 | • Reply: WAL journal file-size keeps on growing... artifact: c51ace1681 user: slavin | |
20:56 | • Reply: Convert datetime string to second since Epoch with millisecond precision artifact: 550d61b893 user: kmedcalf | |
11:22 | • Reply: Announcing LumoSQL 0.3 artifact: 9c977335bb user: danshearer | |
08:38 | • Reply: CASE value within trigger? artifact: 5694270c63 user: kmedcalf | |
08:24 | • Reply: Announcing LumoSQL 0.3 artifact: b109100aec user: dan | |
07:59 | • Post: CASE value within trigger? artifact: 15254d1b6d user: anonymous | |
2020-11-10
| ||
21:17 | • Post: An sqlite extension for transparent row-level compression using zstd artifact: 376e133e8b user: anonymous | |
19:07 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: f00dd6a891 user: kmedcalf | |
19:00 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 8a31f1fe4a user: kmedcalf | |
15:55 | • Reply: WAL journal file-size keeps on growing... artifact: f558bf42df user: gunter_hick | |
15:50 | • Post: Announcing LumoSQL 0.3 artifact: 376fde8826 user: danshearer | |
14:30 | • Post: WAL journal file-size keeps on growing... artifact: 6c571ebbae user: JohnSmith | |
12:56 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 69ec86f630 user: JohnSmith | |
11:46 | • Edit reply: Empty journal files left on disk after connection was gracefully closed artifact: 62eb6e2549 user: kmedcalf | |
11:31 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: f53bf8ae99 user: kmedcalf | |
10:29 | • Edit reply: WAL journal and threading mode artifact: f4bfb82c2c user: kmedcalf | |
10:28 | • Edit reply: WAL journal and threading mode artifact: 90ef18d88d user: kmedcalf | |
10:20 | • Reply: WAL journal and threading mode artifact: d0c0f3de41 user: kmedcalf | |
10:09 | • Reply: WAL journal and threading mode artifact: ed5c6c6cff user: kmedcalf | |
09:51 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 89f86840f5 user: kmedcalf | |
09:44 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 86a1663e15 user: JohnSmith | |
08:24 | • Reply: WAL journal and threading mode artifact: 18bf75ddb9 user: JohnSmith | |
07:46 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 41e5e8ab7d user: cladisch | |
07:37 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 178cf7f8de user: gunter_hick | |
06:53 | • Reply: WAL journal and threading mode artifact: 45ce2f433a user: kmedcalf | |
06:47 | • Reply: WAL journal and threading mode artifact: f60faa87dd user: kmedcalf | |
06:30 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: ed00f47e3c user: JohnSmith | |
05:39 | • Reply: Empty journal files left on disk after connection was gracefully closed artifact: 28c4871e18 user: LarryBrasfield | |
04:51 | • Post: Empty journal files left on disk after connection was gracefully closed artifact: 0a00ce64d7 user: JohnSmith | |