Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
169 events for the month beginning 2023-06-01 by user kmedcalf
Following month ↑|
2023-06-30
| ||
| 20:18 | • Reply: Column/Cell level storage report artifact: c4782d56e3 user: kmedcalf | |
| 15:46 | • Reply: Column/Cell level storage report artifact: ce810390f3 user: kmedcalf | |
| 15:02 | • Reply: Inaccurate Statement artifact: a730ae1928 user: kmedcalf | |
| 00:43 | • Reply: Inaccurate Statement artifact: 3898c52670 user: kmedcalf | |
| 00:33 | • Reply: Inaccurate Statement artifact: 67f3edb41c user: kmedcalf | |
|
2023-06-29
| ||
| 23:47 | • Reply: Inaccurate Statement artifact: 9f8303a1a2 user: kmedcalf | |
| 23:28 | • Reply: Inaccurate Statement artifact: 9f637fc1e0 user: kmedcalf | |
| 22:09 | • Edit: Inaccurate Statement artifact: f81b1e9ac3 user: kmedcalf | |
| 22:00 | • Post: Inaccurate Statement artifact: 83cccac838 user: kmedcalf | |
| 17:55 | • Reply: Conversion msaccess mdb to SQLite artifact: d4a34bfc1a user: kmedcalf | |
|
2023-06-28
| ||
| 21:45 | • Reply: Improve initial insert performance of rtree index artifact: a134237110 user: kmedcalf | |
| 20:01 | • Reply: Confused about concurrency and sychronization artifact: dda0ef4def user: kmedcalf | |
| 19:56 | • Edit reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: fec16a0e0c user: kmedcalf | |
| 19:47 | • Edit reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: 0ddb652ead user: kmedcalf | |
| 19:44 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: 5b5705eb50 user: kmedcalf | |
| 19:32 | • Reply: Incorrect SUM values artifact: 8f9c2db2b5 user: kmedcalf | |
| 19:22 | • Edit reply: Incorrect SUM values artifact: b6ea5fc40b user: kmedcalf | |
| 18:51 | • Edit reply: Incorrect SUM values artifact: b2f9fe461f user: kmedcalf | |
| 18:49 | • Reply: Incorrect SUM values artifact: 8f916d7767 user: kmedcalf | |
| 18:42 | • Reply: Confused about concurrency and sychronization artifact: b3d9dd9401 user: kmedcalf | |
| 18:40 | • Reply: Confused about concurrency and sychronization artifact: 0e49f4cbbb user: kmedcalf | |
| 18:38 | • Reply: Pragma journal_mode=memory forces reset from WAL to delete artifact: ba2524c7a8 user: kmedcalf | |
|
2023-06-27
| ||
| 20:34 | • Edit reply: Resolve hyperlink path from field name artifact: 219c26611b user: kmedcalf | |
| 20:31 | • Edit reply: Resolve hyperlink path from field name artifact: 5610828f6a user: kmedcalf | |
| 20:30 | • Reply: Resolve hyperlink path from field name artifact: 29c2cd9f8b user: kmedcalf | |
| 20:25 | • Reply: Resolve hyperlink path from field name artifact: 1ec947cbe6 user: kmedcalf | |
| 20:21 | • Edit reply: Resolve hyperlink path from field name artifact: b69a7e4987 user: kmedcalf | |
| 20:21 | • Reply: Resolve hyperlink path from field name artifact: 1662a10740 user: kmedcalf | |
| 20:14 | • Reply: Confused about concurrency and sychronization artifact: abf3798bd7 user: kmedcalf | |
| 20:12 | • Reply: Confused about concurrency and sychronization artifact: f8a6866ebd user: kmedcalf | |
| 18:26 | • Reply: Confused about concurrency and sychronization artifact: 4040daabcb user: kmedcalf | |
| 18:24 | • Reply: Confused about concurrency and sychronization artifact: 175b10eadd user: kmedcalf | |
| 17:26 | • Reply: Confused about concurrency and sychronization artifact: fe132a7a7a user: kmedcalf | |
| 17:20 | • Reply: Confused about concurrency and sychronization artifact: f9a190d9f9 user: kmedcalf | |
|
2023-06-26
| ||
| 20:00 | • Reply: Using SQLite in C++ on Windows; where is the .h file? artifact: 41aaa860ae user: kmedcalf | |
| 17:43 | • Edit reply: Using SQLite in C++ on Windows; where is the .h file? artifact: 93557b4cbd user: kmedcalf | |
| 17:41 | • Edit reply: Using SQLite in C++ on Windows; where is the .h file? artifact: 5067db1efd user: kmedcalf | |
| 17:38 | • Reply: Using SQLite in C++ on Windows; where is the .h file? artifact: 6c05fb30da user: kmedcalf | |
|
2023-06-25
| ||
| 15:55 | • Reply: Setting TOP variable does not set tcl scripts correctly artifact: 7d49cce9b6 user: kmedcalf | |
| 14:41 | • Reply: REAL format precision artifact: c75e7474fc user: kmedcalf | |
| 14:28 | • Edit reply: REAL format precision artifact: 15d74a1277 user: kmedcalf | |
| 14:25 | • Reply: REAL format precision artifact: f36d9878fe user: kmedcalf | |
| 14:20 | • Edit reply: REAL format precision artifact: dd6b4d27a3 user: kmedcalf | |
| 14:16 | • Reply: REAL format precision artifact: 50fefae1cf user: kmedcalf | |
| 13:56 | • Reply: new connection with SQLITE_OPEN_READONLY flag query error after the db changed journal mode to WAL artifact: 4e3e050969 user: kmedcalf | |
|
2023-06-24
| ||
| 21:11 | • Reply: Simple Connection Pool for SQLite in Python artifact: 1219bdf54a user: kmedcalf | |
| 20:56 | • Reply: Simple Connection Pool for SQLite in Python artifact: 9e9b862726 user: kmedcalf | |
| 20:41 | • Reply: Simple Connection Pool for SQLite in Python artifact: 696f35e682 user: kmedcalf | |
| 18:29 | • Edit reply: REAL format precision artifact: 4fd0082e24 user: kmedcalf | |
| 18:25 | • Reply: Simple Connection Pool for SQLite in Python artifact: 496c530b59 user: kmedcalf | |
| 18:06 | • Reply: REAL format precision artifact: 45adb879d3 user: kmedcalf | |
|
2023-06-23
| ||
| 23:04 | • Reply: REAL format precision artifact: b5bc5abd00 user: kmedcalf | |
| 18:54 | • Reply: REAL format precision artifact: ce7336bdc4 user: kmedcalf | |
| 18:40 | • Reply: REAL format precision artifact: b5e1fef1f8 user: kmedcalf | |
| 18:38 | • Reply: REAL format precision artifact: ec350c7b84 user: kmedcalf | |
| 18:37 | • Reply: REAL format precision artifact: 70ed46b6ca user: kmedcalf | |
| 17:39 | • Edit reply: REAL format precision artifact: 039a50f607 user: kmedcalf | |
| 17:38 | • Reply: REAL format precision artifact: 160df24774 user: kmedcalf | |
| 17:13 | • Reply: REAL format precision artifact: 9ea9428d08 user: kmedcalf | |
| 16:50 | • Reply: REAL format precision artifact: aaf79863d8 user: kmedcalf | |
| 16:46 | • Reply: REAL format precision artifact: ccef246714 user: kmedcalf | |
| 16:35 | • Edit reply: REAL format precision artifact: 3789b4a822 user: kmedcalf | |
| 16:34 | • Reply: REAL format precision artifact: f716e6d7d9 user: kmedcalf | |
|
2023-06-22
| ||
| 01:35 | • Reply: FEATURE REQUEST: use of DEFAULT in INSERTs artifact: 3769b9827c user: kmedcalf | |
|
2023-06-21
| ||
| 21:20 | • Reply: FEATURE REQUEST: use of DEFAULT in INSERTs artifact: aaf33fd448 user: kmedcalf | |
| 21:01 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: 60f4cac687 user: kmedcalf | |
| 19:59 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: c048dbee59 user: kmedcalf | |
| 18:58 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: adb8a31578 user: kmedcalf | |
| 18:15 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: 405b0aae5a user: kmedcalf | |
| 17:39 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: fb33df77f8 user: kmedcalf | |
| 16:01 | • Reply: "database is locked": detecting deadlock vs. busy timeout? artifact: 4350638e78 user: kmedcalf | |
|
2023-06-20
| ||
| 20:55 | • Reply: postgres ilike operator artifact: c19d357add user: kmedcalf | |
| 20:51 | • Reply: postgres ilike operator artifact: fff5b10e81 user: kmedcalf | |
| 19:07 | • Edit reply: postgres ilike operator artifact: e2d1cd8e30 user: kmedcalf | |
| 19:04 | • Reply: postgres ilike operator artifact: 23a6ce193c user: kmedcalf | |
| 17:13 | • Reply: postgres ilike operator artifact: 5e526b79ef user: kmedcalf | |
| 16:44 | • Edit reply: postgres ilike operator artifact: 456e4440f1 user: kmedcalf | |
| 16:43 | • Reply: postgres ilike operator artifact: 2ba9cb41a5 user: kmedcalf | |
|
2023-06-19
| ||
| 19:40 | • Edit reply: How can I make SQLITE run slower? artifact: f802734768 user: kmedcalf | |
| 19:38 | • Edit reply: How can I make SQLITE run slower? artifact: 89d249aa2a user: kmedcalf | |
| 19:33 | • Reply: How can I make SQLITE run slower? artifact: a1b98082b7 user: kmedcalf | |
|
2023-06-18
| ||
| 17:34 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: c2bcfc6fcf user: kmedcalf | |
| 17:19 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 42fa49b5f5 user: kmedcalf | |
| 17:11 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: 6c6d5c0060 user: kmedcalf | |
| 16:40 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: bb7e69fa6f user: kmedcalf | |
| 16:20 | • Reply: How do SQLite triggers work? artifact: ab2fda3ec1 user: kmedcalf | |
|
2023-06-17
| ||
| 23:53 | • Edit reply: How do SQLite triggers work? artifact: d375e9c1f8 user: kmedcalf | |
| 23:09 | • Edit reply: How do SQLite triggers work? artifact: cbec621981 user: kmedcalf | |
| 21:31 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: d2845d8dc3 user: kmedcalf | |
| 21:15 | • Reply: How do SQLite triggers work? artifact: 83aee6c76e user: kmedcalf | |
| 20:58 | • Reply: How do SQLite triggers work? artifact: 2d12c1a246 user: kmedcalf | |
| 19:24 | • Edit reply: How do SQLite triggers work? artifact: 35f2858f35 user: kmedcalf | |
| 19:23 | • Reply: How do SQLite triggers work? artifact: 38db49b53b user: kmedcalf | |
| 19:21 | • Reply: How do SQLite triggers work? artifact: ab60b08f7d user: kmedcalf | |
| 19:08 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 120d96a8c7 user: kmedcalf | |
|
2023-06-16
| ||
| 18:08 | • Reply: How can I make SQLITE run slower? artifact: 5aa45decbe user: kmedcalf | |
| 18:03 | • Reply: How can I make SQLITE run slower? artifact: 605530dac2 user: kmedcalf | |
| 17:49 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: ad19f8c9af user: kmedcalf | |
|
2023-06-15
| ||
| 20:35 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: a5b6a1a4db user: kmedcalf | |
| 20:31 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: bc0cd17bdd user: kmedcalf | |
|
2023-06-14
| ||
| 18:27 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: a27bae70e2 user: kmedcalf | |
| 16:10 | • Reply: "PRAGMA journal_mode" without effect ? artifact: cff4729873 user: kmedcalf | |
|
2023-06-13
| ||
| 14:51 | • Reply: SELECT usage: unclear terms - theory questions (GROUP BY, ORDER BY). Beginner) artifact: 554e36867e user: kmedcalf | |
|
2023-06-12
| ||
| 20:55 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: d98d7e03a8 user: kmedcalf | |
| 20:47 | • Reply: Better explanation about Readonly and ATTACH database artifact: 1a12bb076b user: kmedcalf | |
| 20:38 | • Reply: Better explanation about Readonly and ATTACH database artifact: 82583b92d2 user: kmedcalf | |
| 20:20 | • Reply: Better explanation about Readonly and ATTACH database artifact: 5a1f157c83 user: kmedcalf | |
| 20:12 | • Reply: Better explanation about Readonly and ATTACH database artifact: 0cc68a6b8e user: kmedcalf | |
| 20:08 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: 3c692a4a04 user: kmedcalf | |
| 20:06 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: e5aaed224b user: kmedcalf | |
| 20:05 | • Reply: Better explanation about Readonly and ATTACH database artifact: 54bdea64c4 user: kmedcalf | |
| 19:33 | • Reply: Better explanation about Readonly and ATTACH database artifact: c95bcb33e6 user: kmedcalf | |
| 19:26 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: 50d14d5c6b user: kmedcalf | |
| 19:24 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: f368c62e90 user: kmedcalf | |
| 19:23 | • Reply: Better explanation about Readonly and ATTACH database artifact: 523f89a4c2 user: kmedcalf | |
| 18:57 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: e72750fd6a user: kmedcalf | |
| 18:57 | • Edit reply: Better explanation about Readonly and ATTACH database artifact: 35da4b8415 user: kmedcalf | |
| 18:54 | • Reply: Better explanation about Readonly and ATTACH database artifact: ae2cd185e7 user: kmedcalf | |
| 18:48 | • Reply: Better explanation about Readonly and ATTACH database artifact: 43aaa589b0 user: kmedcalf | |
| 18:34 | • Reply: regexp bug? or brain flatulence? artifact: e3df5953b8 user: kmedcalf | |
| 16:58 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: 39ea3ba4d2 user: kmedcalf | |
| 15:54 | • Edit reply: Option to make SQLite stricter with non-aggregate columns artifact: cc68a0bf56 user: kmedcalf | |
| 15:42 | • Edit reply: Option to make SQLite stricter with non-aggregate columns artifact: c3f512c45c user: kmedcalf | |
| 15:40 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: f3a452365b user: kmedcalf | |
| 15:33 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: 513395a9ae user: kmedcalf | |
| 14:24 | • Edit reply: When does a pointer to column text become invalid? artifact: 2d89fd2d3a user: kmedcalf | |
| 14:23 | • Reply: When does a pointer to column text become invalid? artifact: 0c0951b79e user: kmedcalf | |
|
2023-06-11
| ||
| 19:03 | • Edit reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: 6f9f4330d6 user: kmedcalf | |
| 19:01 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: e4ec2eba36 user: kmedcalf | |
| 18:00 | • Reply: Default first record artifact: a6101efc5a user: kmedcalf | |
| 17:48 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: edfdc5d58a user: kmedcalf | |
| 17:39 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: fd53a1c8d3 user: kmedcalf | |
| 17:20 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: 25b260ea34 user: kmedcalf | |
| 17:11 | • Edit reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: 3f44097326 user: kmedcalf | |
| 17:09 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: 7a718626d1 user: kmedcalf | |
| 16:56 | • Edit reply: Default first record artifact: 5db9540ffe user: kmedcalf | |
| 16:55 | • Reply: Default first record artifact: ebede7283b user: kmedcalf | |
| 16:23 | • Reply: 3.42 and `ON CONFLICT` behavior with `unixepoch('subsec')` artifact: a62e1504bc user: kmedcalf | |
| 01:14 | • Edit reply: SELECT usage: unclear terms - theory questions (GROUP BY, ORDER BY). Beginner) artifact: 2b4c4faf16 user: kmedcalf | |
| 01:11 | • Reply: SELECT usage: unclear terms - theory questions (GROUP BY, ORDER BY). Beginner) artifact: 1cc7e6ef57 user: kmedcalf | |
|
2023-06-10
| ||
| 16:50 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: cd63218f09 user: kmedcalf | |
|
2023-06-09
| ||
| 17:17 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: 01221383b9 user: kmedcalf | |
| 16:37 | • Reply: Better explanation about Readonly and ATTACH database artifact: b72b44b174 user: kmedcalf | |
| 16:33 | • Reply: Better explanation about Readonly and ATTACH database artifact: f3ceedb47b user: kmedcalf | |
|
2023-06-08
| ||
| 17:03 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: 83029caa7d user: kmedcalf | |
| 16:37 | • Reply: (Deleted) artifact: b7fe2b379f user: kmedcalf | |
| 15:30 | • Reply: Option to make SQLite stricter with non-aggregate columns artifact: 7abdaf67eb user: kmedcalf | |
|
2023-06-07
| ||
| 02:43 | • Edit reply: (Deleted) artifact: 62a5312216 user: kmedcalf | |
| 02:41 | • Reply: (Deleted) artifact: 39df60d450 user: kmedcalf | |
|
2023-06-06
| ||
| 16:45 | • Reply: (Deleted) artifact: 1af14d281f user: kmedcalf | |
| 16:28 | • Reply: (Deleted) artifact: 7706a0a3a8 user: kmedcalf | |
| 15:41 | • Reply: (Deleted) artifact: f323ef96df user: kmedcalf | |
| 15:06 | • Reply: Reverse function seems to work, missing in documentation? artifact: dbb50c0b2d user: kmedcalf | |
| 14:58 | • Reply: Delete triggers and constraints artifact: 8aeab0a534 user: kmedcalf | |
|
2023-06-05
| ||
| 21:10 | • Reply: Delete triggers and constraints artifact: aec919a60d user: kmedcalf | |
| 19:47 | • Reply: (Deleted) artifact: a37574e27e user: kmedcalf | |
| 15:54 | • Edit reply: .param lquoted iterals artifact: c39a2f0143 user: kmedcalf | |
| 15:54 | • Reply: .param lquoted iterals artifact: eecdb2502c user: kmedcalf | |
| 15:44 | • Reply: (Deleted) artifact: 74afd061a0 user: kmedcalf | |
| 15:31 | • Reply: Reverse function seems to work, missing in documentation? artifact: 88f614882e user: kmedcalf | |
|
2023-06-04
| ||
| 13:27 | • Edit reply: .param lquoted iterals artifact: 296b696266 user: kmedcalf | |
| 13:26 | • Edit reply: .param lquoted iterals artifact: 8df634374c user: kmedcalf | |
| 13:24 | • Reply: .param lquoted iterals artifact: ccea0a9149 user: kmedcalf | |
|
2023-06-02
| ||
| 16:18 | • Reply: Feature Request: shell prompt for query parameters artifact: cff54a31d6 user: kmedcalf | |
| 14:30 | • Reply: Reverse function seems to work, missing in documentation? artifact: 821c0893f4 user: kmedcalf | |
| 14:16 | • Reply: Reverse function seems to work, missing in documentation? artifact: 634ec6a7cc user: kmedcalf | |
| 14:08 | • Reply: CURRENT_TIMESTAMP is what? artifact: df52a24536 user: kmedcalf | |
| 14:01 | • Reply: Feature Request: shell prompt for query parameters artifact: c2a7eccabd user: kmedcalf | |
|
2023-06-01
| ||
| 14:56 | • Reply: Forcing read only access artifact: 58ad03e361 user: kmedcalf | |