This Day In History For 2024-03-14
1 Year Ago (more context)
|
2023-03-14
| ||
| 23:47 | • Edit: python sqlite3 db mysteriously ending up as a 0 byte file artifact: 2b3f322b58 user: john_relegardin | |
| 23:14 | • Post: python sqlite3 db mysteriously ending up as a 0 byte file artifact: 0e4c6fc734 user: john_relegardin | |
| 22:33 | • Reply: Request for ENH for consideration. (parse_url, parse_str etc). artifact: bd35cccd1f user: larrybr | |
| 22:20 | • Reply: Request for ENH for consideration. (parse_url, parse_str etc). artifact: 96008f59ab user: midijohnny | |
| 22:18 | • Reply: Request for ENH for consideration. (parse_url, parse_str etc). artifact: 747fede1b1 user: slavin | |
| 22:16 | • Reply: Program with SQLite database running too slow artifact: cd6b0dc3d2 user: slavin | |
| 22:00 | • Edit: Request for ENH for consideration. (parse_url, parse_str etc). artifact: c77cb24883 user: midijohnny | |
| 22:00 | • Edit: Request for ENH for consideration. (parse_url, parse_str etc). artifact: db57d9019b user: midijohnny | |
| 21:59 | • Post: Request for ENH for consideration. (parse_url, parse_str etc). artifact: 0bc0d863be user: midijohnny | |
| 21:54 | • Edit reply: Program with SQLite database running too slow artifact: e29e8a4d7a user: larrybr | |
| 21:05 | • Reply: FYI: LD_PRELOAD library to exfiltrate queries with query plans and statistics artifact: ad5981c62f user: bjoern | |
| 20:18 | • Reply: Incorrect query result artifact: 781ac7720f user: drh | |
| 20:17 | • Reply: ANALYZE causes incorrect query results. artifact: f77001b105 user: drh | |
| 20:14 | • Reply: Program with SQLite database running too slow artifact: 9146599de7 user: larrybr | |
| 19:46 | • Reply: SQLite Wasm for Safari And Firefox progress artifact: 3759f37a7c user: steida | |
| 19:24 | • Reply: Incorrect query result artifact: a2a9e09e92 user: dfgriggs | |
| 19:24 | • Post: Program with SQLite database running too slow artifact: 2116a91f02 user: lea12345 | |
| 18:34 | • Reply: SQLite Wasm for Safari And Firefox progress artifact: 88cdbe0d9d user: stephan | |
| 18:05 | • Reply: are simple subqueries faster than join? artifact: 42fba2ac43 user: kmedcalf | |
| 17:59 | • Reply: SQLite Wasm for Safari And Firefox progress artifact: 98106e61ec user: steida | |
| 17:48 | • Reply: are simple subqueries faster than join? artifact: 89984238f4 user: kaizhu256 | |
| 16:54 | • Reply: SQLite WASM benchmarks artifact: 19f3cb03ec user: steida | |
| 16:42 | • Reply: SQLite WASM artifact: 1a90d97345 user: stephan | |
| 16:25 | • Edit: SQLite WASM artifact: a7010b9a53 user: mmomtchev | |
| 16:20 | • Edit: SQLite WASM artifact: 021cb1926b user: mmomtchev | |
| 16:20 | • Post: SQLite WASM artifact: 7246298b07 user: mmomtchev | |
| 16:10 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 0138fd5fc9 user: chacha21 | |
| 15:59 | • Reply: are simple subqueries faster than join? artifact: 95c599d831 user: kmedcalf | |
| 15:47 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: ee996c542e user: kmedcalf | |
| 15:32 | • Reply: are simple subqueries faster than join? artifact: aba28e83f3 user: kmedcalf | |
| 15:12 | • Edit reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: bba893698d user: bjoern | |
| 15:11 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: bd6f8def2c user: bjoern | |
| 15:00 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 8637b6db90 user: kmedcalf | |
| 14:46 | • Post: are simple subqueries faster than join? artifact: 690b97e38c user: kaizhu256 | |
| 14:28 | • Post: Transaction documentation typo artifact: 13d539fe49 user: anonymous | |
| 14:27 | • Edit reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 55201c5f3e user: kmedcalf | |
| 14:18 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 96687917db user: chacha21 | |
| 14:15 | • Edit reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 8baab5b115 user: kmedcalf | |
| 14:13 | • Edit reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 233fb31b5a user: kmedcalf | |
| 14:05 | • Reply: web-locks polyfill artifact: aa0a11fd51 user: stephan | |
| 13:59 | • Reply: SQLite WASM benchmarks artifact: 4b40965ce6 user: stephan | |
| 13:43 | • Reply: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 78e97ca433 user: kmedcalf | |
| 13:36 | • Reply: web-locks polyfill artifact: e4118d2671 user: steida | |
| 13:34 | • Post: SQLite WASM benchmarks artifact: ad38385d9c user: tantaman | |
| 11:27 | • Edit: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: 8a050dbaad user: chacha21 | |
| 10:51 | • Post: Option to enable sqlite3_mutex_... API with SQLITE_THREADSAFE=0 artifact: d742944fe0 user: chacha21 | |
| 10:10 | • Reply: sqlite3 and O_CREAT artifact: 0aeabccd36 user: valery | |
| 08:12 | • Reply: Help with query plan artifact: 2d270f2231 user: ddevienne | |
| 08:10 | • Reply: Question on activating the LIKE Optimization artifact: 091a96d989 user: cgitsis | |
| 08:09 | • Reply: Question on activating the LIKE Optimization artifact: d61f446441 user: cgitsis | |
| 08:05 | • Post: Incorrect query result artifact: d47a0e8e3a user: John-Jove | |
| 07:16 | • Post: ANALYZE causes incorrect query results. artifact: 2e427099d5 user: John-Jove | |
| 04:55 | • Reply: Question on activating the LIKE Optimization artifact: 17056d1aa7 user: anonymous | |
| 03:26 | • Post: GROUP BY is better than DISTINCT in some cases. artifact: 10e8028020 user: bjoern | |
| 00:15 | • Reply: INSERT Optimization Opportunity artifact: ffdddc309b user: kmedcalf | |
2 Years Ago (more context)
|
2022-03-14
| ||
| 23:52 | • Reply: sqlite3_value_dup and stale pointers artifact: 3e4c2104f9 user: drh | |
| 23:25 | • Post: Prevent Automatic Rounding? artifact: 7b49338524 user: jhersey29 | |
| 23:18 | • Edit reply: Fast way to insert rows in SQLite artifact: 29e1e32116 user: sqlitening | |
| 23:12 | • Edit reply: Fast way to insert rows in SQLite artifact: dde2b73c5b user: sqlitening | |
| 23:12 | • Edit reply: Fast way to insert rows in SQLite artifact: 94d6d2207b user: sqlitening | |
| 23:10 | • Edit reply: Fast way to insert rows in SQLite artifact: 5b4e54de6f user: sqlitening | |
| 23:08 | • Edit reply: Fast way to insert rows in SQLite artifact: b922d1be85 user: sqlitening | |
| 23:07 | • Edit reply: Fast way to insert rows in SQLite artifact: e31ae6cd65 user: sqlitening | |
| 23:06 | • Edit reply: Fast way to insert rows in SQLite artifact: ec2a458cb9 user: sqlitening | |
| 23:03 | • Edit reply: Fast way to insert rows in SQLite artifact: 2b0375362f user: sqlitening | |
| 23:02 | • Edit reply: Fast way to insert rows in SQLite artifact: 7295aa1f56 user: sqlitening | |
| 23:00 | • Reply: Fast way to insert rows in SQLite artifact: 42f61e77f7 user: sqlitening | |
| 21:39 | • Reply: Annual Maintenance Subscription and High-priority Technical Support artifact: a565b93416 user: drh | |
| 21:22 | • Reply: Installing in Visual Studio 2022 artifact: 71e6a2656c user: mistachkin | |
| 20:37 | • Reply: Annual Maintenance Subscription and High-priority Technical Support artifact: 3cba1073f5 user: drh | |
| 20:13 | • Reply: Annual Maintenance Subscription and High-priority Technical Support artifact: ddcdd2ab56 user: anonymous | |
| 20:01 | • Reply: Installing in Visual Studio 2022 artifact: e630a7889a user: kmedcalf | |
| 19:59 | • Edit reply: Annual Maintenance Subscription and High-priority Technical Support artifact: 2d243fc551 user: drh | |
| 19:58 | • Edit reply: Annual Maintenance Subscription and High-priority Technical Support artifact: 726cc565ff user: drh | |
| 19:57 | • Post: JSON_Object() Argument Limit artifact: 716cb210a7 user: dCipher | |
| 19:51 | • Reply: Annual Maintenance Subscription and High-priority Technical Support artifact: 93b161d572 user: drh | |
| 19:50 | • Edit: (Deleted) artifact: 6d33b2090f user: dCipher | |
| 19:36 | • Post: Annual Maintenance Subscription and High-priority Technical Support artifact: cf8b3b9c12 user: anonymous | |
| 19:35 | • Reply: Installing in Visual Studio 2022 artifact: fd8bb02e02 user: larrybr | |
| 19:32 | • Post: sqlite3_value_dup and stale pointers artifact: ae8592cc73 user: anonymous | |
| 19:20 | • Post: (Deleted) artifact: 6f27518855 user: dCipher | |
| 19:11 | • Post: Installing in Visual Studio 2022 artifact: 81fa764b49 user: anonymous | |
| 18:11 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 7f18737e6c user: kmedcalf | |
| 18:00 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 67c2310644 user: kmedcalf | |
| 17:57 | • Post: DROP COLUMN documentation lacking version information artifact: acdd3dc72d user: bohwaz | |
| 17:00 | • Reply: Creating column constraint to allow only digits artifact: 6985d13d3c user: cuz | |
| 16:55 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: b6126b6958 user: drh | |
| 15:37 | • Reply: Creating column constraint to allow only digits artifact: 9e22cfca77 user: holgerj | |
| 14:42 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: e5e99c6497 user: coleifer | |
| 13:53 | • Reply: .connection artifact: 9470ec4b65 user: drh | |
| 13:24 | • Reply: Introduction a Quick SQLite Cmd/Script Tools artifact: 3bc5d99e5a user: wolf71 | |
| 12:57 | • Reply: Creating column constraint to allow only digits artifact: 752ff79a6d user: dkfellows | |
| 12:44 | • Reply: What is "in-process" in "SQLite is an in-process library"? artifact: c0280c17bf user: dkfellows | |
| 12:33 | • Reply: Suggestion: Use strong hashes on the download page artifact: 968876964a user: dkfellows | |
| 12:17 | • Reply: .connection artifact: febade7e20 user: dkfellows | |
| 11:35 | • Post: .connection artifact: bd465fed2c user: anonymous | |
| 11:32 | • Reply: scope of aliases - ambiguity? (Possible to trap this?) artifact: 8d993cb555 user: midijohnny | |
| 11:31 | • Edit: scope of aliases - ambiguity? (Possible to trap this?) artifact: 06107cf56e user: midijohnny | |
| 11:30 | • Post: scope of aliases - ambiguity? (Possible to trap this?) artifact: 4e28039554 user: midijohnny | |
| 04:47 | • Reply: Will BackUpdatabase API locks the database artifact: 5cbe46c29b user: anonymous | |
| 04:45 | • Reply: Will BackUpdatabase API locks the database artifact: 3a89e48e34 user: Vijay_123 | |
| 04:30 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 59635206e3 user: kmedcalf | |
| 04:19 | • Reply: Will BackUpdatabase API locks the database artifact: 05239d6316 user: Vijay_123 | |
| 04:16 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 83f51f1eb2 user: kmedcalf | |
| 04:05 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 35ede5b740 user: kmedcalf | |
| 04:02 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 154b233157 user: larrybr | |
| 04:00 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 1db0023547 user: kmedcalf | |
| 03:56 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 694b9cd61a user: kmedcalf | |
| 03:52 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 5c20ac8d4b user: kmedcalf | |
| 02:53 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 39926f4fae user: kmedcalf | |
| 02:36 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: f823568663 user: kmedcalf | |
| 02:26 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 179c1b12ee user: kmedcalf | |
| 02:18 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: def4cdcc0f user: kmedcalf | |
| 02:17 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: ecbf195518 user: kmedcalf | |
| 02:17 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: c879686816 user: kmedcalf | |
| 02:16 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 042ef636e9 user: kmedcalf | |
| 02:00 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: c6d6e54874 user: larrybr | |
| 01:30 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 3d6e45d19e user: kmedcalf | |
| 01:28 | • Edit reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: f99e200abb user: kmedcalf | |
| 01:25 | • Reply: Change in INSERT/RETURNING foreign key conflict behaviour artifact: 8c6c884fa2 user: kmedcalf | |
3 Years Ago (more context)
|
2021-03-14
| ||
| 23:58 | • Reply: "SQL Features That SQLite Does Not Implement" needs updating artifact: 3d089b54c4 user: d3x0r | |
| 23:06 | • Reply: Runtime of and opcode counts of ANALYZE artifact: 4f546f0038 user: larrybr | |
| 21:44 | • Reply: Runtime of and opcode counts of ANALYZE artifact: ca2d60556c user: jrandall | |
| 21:05 | • Reply: Runtime of and opcode counts of ANALYZE artifact: 1ace76a669 user: macsql20 | |
| 20:49 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 25bdf4636a user: kmedcalf | |
| 20:16 | • Edit reply: "SQL Features That SQLite Does Not Implement" needs updating artifact: 16810004da user: larrybr | |
| 20:13 | • Reply: "SQL Features That SQLite Does Not Implement" needs updating artifact: 973e2aa58c user: larrybr | |
| 19:58 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 039cf7c819 user: larrybr | |
| 19:56 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 27b96c22cd user: Clothears | |
| 19:45 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: a48605104a user: vman59 | |
| 19:10 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: e506ebbed6 user: larrybr | |
| 18:41 | • Edit reply: Runtime of and opcode counts of ANALYZE artifact: aaac0fa4db user: larrybr | |
| 18:34 | • Reply: Runtime of and opcode counts of ANALYZE artifact: 8a12290c7b user: larrybr | |
| 17:30 | • Post: Runtime of and opcode counts of ANALYZE artifact: f1aa52dd12 user: macsql20 | |
| 16:17 | • Reply: How to insert control characters? artifact: 756fb1a496 user: kmedcalf | |
| 14:53 | • Post: How to insert control characters? artifact: 1266dd6092 user: 6kEs4Majrd | |
| 11:19 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 4d678d18ce user: stephancb | |
| 10:54 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 7de330ef72 user: jdennis | |
| 10:28 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 08b895405c user: larrybr | |
| 09:46 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 6be344edc6 user: jdennis | |
| 08:21 | • Reply: Feature request: pragma for changing the precision / format of CURRENT_TIMESTAMP to YYYY-MM-SSTHH:MM:SS.SSS artifact: 8f08cead7d user: stephancb | |
| 01:21 | • Reply: DROP COLUMN on indexed column doesn't raise an error artifact: f70cd336ba user: drh | |
4 Years Ago (more context)
|
2020-03-14
| ||
| 22:45 | • Reply: sqlite write performance is slower than the filesystem artifact: 3073c23742 user: jimdod | |
| 22:35 | • Reply: sqlite write performance is slower than the filesystem artifact: 59336baa25 user: kmedcalf | |
| 22:01 | • Reply: sqlite write performance is slower than the filesystem artifact: 315767ded3 user: bioinfornatics | |
| 21:47 | • Reply: sqlite write performance is slower than the filesystem artifact: 82f02c590d user: kmedcalf | |
| 21:41 | • Edit reply: sqlite write performance is slower than the filesystem artifact: f1efa969de user: bioinfornatics | |
| 21:41 | • Edit reply: sqlite write performance is slower than the filesystem artifact: dd91758192 user: bioinfornatics | |
| 21:40 | • Reply: sqlite write performance is slower than the filesystem artifact: 04a6bb5af6 user: bioinfornatics | |
| 20:53 | • Reply: sqlite write performance is slower than the filesystem artifact: cd9fae07b1 user: drh | |
| 20:34 | • Edit reply: sqlite write performance is slower than the filesystem artifact: 1a70a98f87 user: bioinfornatics | |
| 20:11 | • Delete reply: sqlite write performance is slower than the filesystem artifact: 7867c186af user: bioinfornatics | |
| 20:11 | • Edit reply: sqlite write performance is slower than the filesystem artifact: 7e57c17483 user: bioinfornatics | |
| 20:10 | • Reply: sqlite write performance is slower than the filesystem artifact: c76876403f user: bioinfornatics | |
| 20:10 | • Reply: sqlite write performance is slower than the filesystem artifact: 56acd13e0f user: bioinfornatics | |
| 19:33 | • Reply: sqlite write performance is slower than the filesystem artifact: e8bba5bedb user: wmertens | |
| 18:32 | • Edit: sqlite write performance is slower than the filesystem artifact: 8976d99d27 user: drh | |
| 18:30 | • Post: sqlite write performance is slower than the filesystem artifact: 1a1c61cb01 user: bioinfornatics | |
| 16:44 | • Reply: Help needed! Database corruption on embedded system artifact: 79f97c75a7 user: slavin | |
| 16:43 | • Reply: Compiling without the amalgamation process artifact: 6a1962512e user: kmedcalf | |
| 16:09 | • Reply: How can I change the email address on my account? artifact: a1c3310311 user: anonymous | |
| 16:07 | • Reply: Forum emails are all going to the SPAM folder artifact: 43b3c29107 user: huynhtrankhanh1 | |
| 16:07 | • Reply: Compiling without the amalgamation process artifact: f5168060db user: anonymous | |
| 15:57 | • Reply: Compiling without the amalgamation process artifact: 9dced49386 user: anonymous | |
| 15:29 | • Reply: Help needed! Database corruption on embedded system artifact: cf47b50ab3 user: dan | |
| 15:07 | • Edit reply: Help needed! Database corruption on embedded system artifact: a4097ed6a9 user: drh | |
| 15:05 | • Edit: Help needed! Database corruption on embedded system artifact: 8f12cc1c3c user: drh | |
| 14:24 | • Reply: Help needed! Database corruption on embedded system artifact: 06552b36e2 user: vasile.rares93 | |
| 13:55 | • Reply: Forum emails are all going to the SPAM folder artifact: 40c458fd09 user: stephan | |
| 10:52 | • Reply: Help needed! Database corruption on embedded system artifact: c73da0086b user: dan | |
| 10:36 | • Post: Help needed! Database corruption on embedded system artifact: aaf6857b4b user: vasile.rares93 | |
| 00:05 | • Reply: Forum emails are all going to the SPAM folder artifact: b6ba13e1ea user: knu | |