This Day In History For 2025-06-14
1 Year Ago (more context)
|
2024-06-14
| ||
| 20:27 | • Reply: Slow combined query from two fast SELECT queries artifact: 95e13df51b user: anonymous | |
| 14:56 | • Post: Slow combined query from two fast SELECT queries artifact: aed0410ce3 user: anonymous | |
| 13:35 | • Reply: Fuzzy Deduplication Efficiently artifact: 20515c846a user: rogerbinns | |
| 12:30 | • Post: Fuzzy Deduplication Efficiently artifact: 3b75aee486 user: gcoakes | |
| 11:44 | • Reply: FORTRAN with SQLite artifact: 701618d489 user: mark | |
| 08:50 | • Edit reply: FORTRAN with SQLite artifact: b3b2d6c84d user: stephancb | |
| 07:47 | • Reply: FORTRAN with SQLite artifact: cc2d94bd83 user: stephancb | |
| 06:20 | • Edit reply: Using EF Core vs raw SQL artifact: 0f75458cd3 user: AAsk1902 | |
| 06:18 | • Edit reply: Using EF Core vs raw SQL artifact: 894e932887 user: AAsk1902 | |
| 06:14 | • Reply: Using EF Core vs raw SQL artifact: 178a06f813 user: AAsk1902 | |
2 Years Ago (more context)
|
2023-06-14
| ||
| 21:20 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: a5cd10f2ae user: punkish | |
| 21:09 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 4447cd2d8c user: slavin | |
| 21:03 | • Reply: Optimizing JSON filter by syntheszing a LIKE artifact: bff647bfe2 user: nuclight | |
| 21:02 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 48d2faaeac user: sqlitening | |
| 20:46 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: e7f42667b7 user: punkish | |
| 20:43 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 5067dd9e2c user: punkish | |
| 20:38 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 919d0de0b8 user: punkish | |
| 20:15 | • Reply: System.Data.SQLite version 1.0.118.0 released artifact: 15e84cab9a user: anonymous | |
| 19:52 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: 22aa7a62c7 user: vman59 | |
| 18:41 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: 4a1e8cf496 user: dvdraymond | |
| 18:40 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 7c556baaec user: dvdraymond | |
| 18:27 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 47ce62dc02 user: spindrift | |
| 18:27 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: a27bae70e2 user: kmedcalf | |
| 18:00 | • Edit reply: "PRAGMA journal_mode" without effect ? artifact: 1a846b9487 user: stephan | |
| 17:57 | • Post: dropping indexes before inserting… good, bad, maybe? artifact: cca52d783c user: punkish | |
| 17:27 | • Reply: json_extract() doesn't work on json_valid artifact: f155282c29 user: punkish | |
| 16:25 | • Reply: System.Data.SQLite version 1.0.118.0 released artifact: 66a0d2716a user: anonymous | |
| 16:10 | • Reply: json_extract() doesn't work on json_valid artifact: 0580863f24 user: tantaman | |
| 16:10 | • Reply: "PRAGMA journal_mode" without effect ? artifact: cff4729873 user: kmedcalf | |
| 15:01 | • Edit reply: json_extract() doesn't work on json_valid artifact: fcfbc81349 user: dbabits | |
| 14:21 | • Reply: "PRAGMA journal_mode" without effect ? artifact: 496d16903b user: anonymous | |
| 14:16 | • Reply: "PRAGMA journal_mode" without effect ? artifact: 4a653ff280 user: holgerj | |
| 13:15 | • Reply: SQLITE_TRACE_ROW artifact: 3432eee51a user: AAsk1902 | |
| 12:27 | • Reply: SQLITE_TRACE_ROW artifact: d2ee894548 user: gunter_hick | |
| 12:17 | • Edit reply: SQLITE_TRACE_ROW artifact: 499058a0a0 user: AAsk1902 | |
| 12:16 | • Edit reply: SQLITE_TRACE_ROW artifact: e5cb59c6ba user: AAsk1902 | |
| 12:14 | • Reply: SQLITE_TRACE_ROW artifact: e9b2ac862e user: AAsk1902 | |
| 10:25 | • Reply: "PRAGMA journal_mode" without effect ? artifact: ec1e9a6c61 user: anonymous | |
| 10:14 | • Reply: SQLITE_TRACE_ROW artifact: 49c655e30b user: gunter_hick | |
| 09:52 | • Reply: "PRAGMA journal_mode" without effect ? artifact: 87df483758 user: knu | |
| 09:47 | • Reply: Exceptions in using the 'charIndex' function in the. NET framework artifact: d1d113b19a user: chrisjlocke1 | |
| 08:35 | • Reply: SQLITE_TRACE_ROW artifact: 795b8ebd02 user: AAsk1902 | |
| 08:27 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: a45bd5bb7f user: gunter_hick | |
| 08:11 | • Reply: SQLITE_TRACE_ROW artifact: dc634a0ae0 user: gunter_hick | |
| 07:55 | • Edit: SQLITE_TRACE_ROW artifact: cf1fadd372 user: AAsk1902 | |
| 07:52 | • Post: "PRAGMA journal_mode" without effect ? artifact: 529d4c37b9 user: anonymous | |
| 07:52 | • Post: SQLITE_TRACE_ROW artifact: 32af4108d5 user: AAsk1902 | |
| 07:10 | • Reply: Exceptions in using the 'charIndex' function in the. NET framework artifact: 4533d7f4c6 user: miss4826 | |
3 Years Ago (more context)
|
2022-06-14
| ||
| 23:57 | • Reply: Assertion `pCtx->pParse->rc==SQLITE_OK' failed artifact: ac7b9b23e2 user: bajinsheng | |
| 23:41 | • Reply: Documentation "typo" artifact: 3c6d448f29 user: anonymous | |
| 22:51 | • Reply: Documentation "typo" artifact: fb7c8699d0 user: kmedcalf | |
| 21:38 | • Edit reply: Basic info request artifact: 910570b287 user: stephan | |
| 21:37 | • Reply: Basic info request artifact: 6942d65e5d user: stephan | |
| 21:37 | • Edit: Basic info request artifact: 1d7e99126e user: stephan | |
| 21:27 | • Post: Documentation "typo" artifact: a2f3af12b1 user: jbodemann | |
| 21:19 | • Reply: Basic info request artifact: 208b562be7 user: slavin | |
| 15:38 | • Reply: SQLite synthesizes IN construct for virtual table queries. artifact: 74ac5db27f user: larrybr | |
| 15:32 | • Reply: Unexpected Result by Complicated JOINING Again artifact: 9f77fe317f user: larrybr | |
| 15:27 | • Post: Basic info request artifact: aa686774e1 user: FBumpus | |
| 12:06 | • Edit reply: Assertion `pCtx->pParse->rc==SQLITE_OK' failed artifact: ecca48d78b user: drh | |
| 11:59 | • Reply: Assertion `pCtx->pParse->rc==SQLITE_OK' failed artifact: 9927ee8f0a user: drh | |
| 11:39 | • Post: Assertion `pCtx->pParse->rc==SQLITE_OK' failed artifact: 3326fadbf3 user: bajinsheng | |
| 09:20 | • Edit reply: Unexpected Result by Complicated JOINING Again artifact: 509f99aec1 user: cuz | |
| 09:19 | • Reply: Unexpected Result by Complicated JOINING Again artifact: c3205f756f user: cuz | |
| 07:42 | • Reply: strftime and utc artifact: 5813a2feaf user: hanche | |
| 07:35 | • Reply: Unexpected Result by Complicated JOINING Again artifact: 54127c5477 user: hanche | |
| 07:28 | • Reply: Unexpected Result by Complicated JOINING Again artifact: 335ce25bfe user: bajinsheng | |
4 Years Ago (more context)
|
2021-06-14
| ||
| 20:33 | • Reply: Extract files from sqlar with a directory prepended artifact: 2606d60a0b user: 6kEs4Majrd | |
| 16:44 | • Reply: Extract files from sqlar with a directory prepended artifact: bbec44fa25 user: lexfiend | |
| 16:04 | • Reply: Extract files from sqlar with a directory prepended artifact: c73b91b3c2 user: 6kEs4Majrd | |
| 15:34 | • Post: Version 3.36.0 now in beta artifact: 4326adcd2b user: drh | |
| 14:17 | • Reply: xBestIndex constraints: discern between JOIN and regular constraints artifact: 09893e4d3b user: gunter_hick | |
| 14:10 | • Reply: Affinity problem existing in functions likely() artifact: 1df339770c user: krking | |
| 14:02 | • Reply: Affinity problem existing in functions likely() artifact: 0ec3fd2c80 user: drh | |
| 13:23 | • Edit reply: SQLite error (7): failed to HeapReAlloc 465625658 bytes (8), heap=7A20000 artifact: ee08318645 user: casaderobison | |
| 13:23 | • Reply: SQLite error (7): failed to HeapReAlloc 465625658 bytes (8), heap=7A20000 artifact: 2728d9471a user: casaderobison | |
| 12:24 | • Reply: xBestIndex constraints: discern between JOIN and regular constraints artifact: 6b588e30b0 user: drh | |
| 12:08 | • Edit: Affinity problem existing in functions likely() artifact: 3b940c437a user: krking | |
| 12:02 | • Post: Affinity problem existing in functions likely() artifact: 37dc1ebe44 user: krking | |
| 11:12 | • Post: xBestIndex constraints: discern between JOIN and regular constraints artifact: 57f4cb4d40 user: gunter_hick | |
| 11:00 | • Reply: create table artifact: aeac6d1d05 user: Clothears | |
| 10:28 | • Reply: create table artifact: 1c472938e8 user: gunter_hick | |
| 10:14 | • Post: create table artifact: 35df2ea2d7 user: Fardin | |
| 08:27 | • Post: SQLite error (7): failed to HeapReAlloc 465625658 bytes (8), heap=7A20000 artifact: e1dc71492a user: lannetscan | |
| 04:30 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: c43c59f6cc user: kmedcalf | |
| 04:23 | • Edit reply: Novice question concerning adding conditional incremental integer counter artifact: 2baded7f45 user: kmedcalf | |
| 04:13 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: 42727de115 user: kmedcalf | |
| 04:07 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: cfbeb49769 user: 1codedebugger | |
| 03:53 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: af2669f9bb user: 1codedebugger | |
| 03:42 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: f463012fda user: kmedcalf | |
| 03:40 | • Post: Bug: incorrect filter expression in arExtractCommand() artifact: 6e9aa98e62 user: lexfiend | |
| 03:35 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: 3e603318ac user: kmedcalf | |
| 03:30 | • Reply: Novice question concerning adding conditional incremental integer counter artifact: a7fddeecb9 user: kmedcalf | |
| 03:22 | • Edit reply: Extract files from sqlar with a directory prepended artifact: e213cc4c03 user: lexfiend | |
| 03:17 | • Reply: Extract files from sqlar with a directory prepended artifact: f71d541d71 user: lexfiend | |
| 02:49 | • Post: Novice question concerning adding conditional incremental integer counter artifact: 49896fcb63 user: 1codedebugger | |
| 00:08 | • Reply: Bug: ALTER TABLE RENAME COLUM TO vs CTE VIEWs artifact: f8a2df559c user: bjoern | |
5 Years Ago (more context)
|
2020-06-14
| ||
| 23:42 | • Reply: Database change counter in WAL mode artifact: 1036369569 user: drh | |
| 23:29 | • Post: Database change counter in WAL mode artifact: c08a3ce613 user: anonymous | |
| 20:16 | • Reply: Possible vulnerabilities from December 2019 artifact: ae2be7db64 user: jungleboogie | |
| 20:13 | • Reply: storing number with 2 decimal place artifact: 26914d5032 user: LarryBrasfield | |
| 20:03 | • Reply: storing number with 2 decimal place artifact: 2cdc1a86c2 user: tonyp | |
| 19:23 | • Reply: Possible vulnerabilities from December 2019 artifact: 81089b4e87 user: kmedcalf | |
| 18:52 | • Reply: Possible vulnerabilities from December 2019 artifact: 2663dda51b user: LarryBrasfield | |
| 18:44 | • Reply: The word 'STORED' not show up in the lang_keywords.html page. artifact: 6a4a13ca56 user: LarryBrasfield | |
| 18:13 | • Reply: Possible vulnerabilities from December 2019 artifact: 92c120c826 user: slavin | |
| 18:08 | • Reply: The word 'STORED' not show up in the lang_keywords.html page. artifact: af3e8173d6 user: drh | |
| 18:00 | • Reply: Possible vulnerabilities from December 2019 artifact: f9fc61be1f user: anonymous | |
| 17:54 | • Reply: Possible vulnerabilities from December 2019 artifact: 0066a47eb3 user: anonymous | |
| 17:39 | • Reply: Possible vulnerabilities from December 2019 artifact: 6d1a49175f user: LarryBrasfield | |
| 17:24 | • Edit reply: Possible vulnerabilities from December 2019 artifact: ec4e2b201d user: kmedcalf | |
| 17:22 | • Reply: Possible vulnerabilities from December 2019 artifact: cd13133502 user: kmedcalf | |
| 17:18 | • Reply: Possible vulnerabilities from December 2019 artifact: 8fd64a7328 user: kmedcalf | |
| 17:17 | • Reply: Possible vulnerabilities from December 2019 artifact: acdab329f5 user: drh | |
| 17:15 | • Reply: Possible vulnerabilities from December 2019 artifact: 9060072f58 user: kmedcalf | |
| 16:49 | • Reply: How db access is handled by sqlite3? artifact: 87d3923d46 user: kmedcalf | |
| 16:47 | • Reply: Possible vulnerabilities from December 2019 artifact: e6134a88f8 user: anonymous | |
| 16:43 | • Reply: storing number with 2 decimal place artifact: caff487612 user: kmedcalf | |
| 16:29 | • Reply: Possible vulnerabilities from December 2019 artifact: 6fa39da94b user: anonymous | |
| 16:22 | • Reply: DROP VIEW IF EXISTS failure artifact: 46c064c87e user: kmedcalf | |
| 16:04 | • Reply: storing number with 2 decimal place in Sqlite3 with python3 artifact: d5cdfdbc4b user: kmedcalf | |
| 15:57 | • Edit reply: Possible vulnerabilities from December 2019 artifact: dc4b4121c0 user: LarryBrasfield | |
| 15:54 | • Reply: Query planner stability guarantee with SQLITE_ENABLE_STAT4 artifact: 194730cc00 user: kmedcalf | |
| 15:54 | • Reply: Possible vulnerabilities from December 2019 artifact: e15a67ef6c user: LarryBrasfield | |
| 15:47 | • Reply: Possible vulnerabilities from December 2019 artifact: 96db57611c user: RichardDamon | |
| 15:32 | • Reply: How db access is handled by sqlite3? artifact: eb659095e7 user: 6kEs4Majrd | |
| 15:02 | • Edit reply: Possible vulnerabilities from December 2019 artifact: 59b1779440 user: LarryBrasfield | |
| 15:00 | • Reply: Possible vulnerabilities from December 2019 artifact: efdb8097a4 user: anonymous | |
| 14:43 | • Edit reply: Possible vulnerabilities from December 2019 artifact: 86dd273cdc user: LarryBrasfield | |
| 14:42 | • Reply: Possible vulnerabilities from December 2019 artifact: fed1cc2186 user: LarryBrasfield | |
| 13:56 | • Reply: Possible vulnerabilities from December 2019 artifact: 4cd02a21d4 user: anonymous | |
| 13:51 | • Reply: Possible vulnerabilities from December 2019 artifact: cd490d4754 user: drh | |
| 13:48 | • Reply: Possible vulnerabilities from December 2019 artifact: f9cb83dd08 user: anonymous | |
| 13:07 | • Reply: storing number with 2 decimal place artifact: ff9c96c2c3 user: luuk | |
| 12:43 | • Reply: DROP VIEW IF EXISTS failure artifact: 171a47ea48 user: LarryBrasfield | |
| 12:18 | • Reply: storing number with 2 decimal place artifact: 955662dc7a user: slavin | |
| 12:09 | • Reply: DROP VIEW IF EXISTS failure artifact: 7b65bc1c18 user: slavin | |
| 12:02 | • Reply: storing number with 2 decimal place artifact: 7bdaaccf66 user: LarryBrasfield | |
| 11:19 | • Post: A tiny spell mistake in the example part at https://sqlite.org/cksumvfs.html#loading artifact: 9d33e89f19 user: anonymous | |
| 11:05 | • Post: The word 'STORED' not show up in the lang_keywords.html page. artifact: 81b532a216 user: anonymous | |
| 09:31 | • Reply: storing number with 2 decimal place artifact: eb238e6311 user: kbk4588 | |
| 09:21 | • Post: storing number with 2 decimal place in Sqlite3 with python3 artifact: 59e544641d user: kbk4588 | |
| 09:20 | • Reply: storing number with 2 decimal place artifact: 9893a33e02 user: Clothears | |
| 08:58 | • Reply: storing number with 2 decimal place artifact: 0a42ffa693 user: luuk | |
| 08:06 | • Reply: storing number with 2 decimal place artifact: eb45ead5ec user: tonyp | |
| 06:40 | • Post: storing number with 2 decimal place artifact: 420e2a54de user: anonymous | |
| 06:00 | • Reply: closure table, prevent identical childrens names per parent artifact: b886fe2798 user: ingo | |
| 05:41 | • Reply: Possible vulnerabilities from December 2019 artifact: 32740e4728 user: slavin | |
| 01:53 | • Post: Query planner stability guarantee with SQLITE_ENABLE_STAT4 artifact: 8de3033266 user: anonymous | |
| 01:38 | • Reply: Possible vulnerabilities from December 2019 artifact: 99699014dd user: anonymous | |