This Day In History For 2024-03-22
1 Year Ago (more context)
|
2023-03-22
| ||
| 23:52 | • Reply: WASM opfs & multiple tabs artifact: ddfece27d4 user: stephan | |
| 23:43 | • Reply: Building sqlite_analyzer.exe with just GCC commands artifact: f098fb4d81 user: kmedcalf | |
| 23:41 | • Reply: WASM opfs & multiple tabs artifact: 78e0c24507 user: scafaria | |
| 23:26 | • Reply: Building sqlite_analyzer.exe with just GCC commands artifact: 9c9614891a user: larrybr | |
| 23:11 | • Reply: Building sqlite_analyzer.exe with just GCC commands artifact: e77455193a user: stephan | |
| 22:42 | • Edit: Building sqlite_analyzer.exe with just GCC commands artifact: 54b7788713 user: wlhmnrrd | |
| 22:41 | • Reply: Feature request: Stored Procedures artifact: 9ac486fe45 user: anonymous | |
| 22:32 | • Post: Building sqlite_analyzer.exe with just GCC commands artifact: a227a6e75e user: wlhmnrrd | |
| 22:26 | • Reply: How can I check if a database is valid? artifact: 31f3457892 user: kmedcalf | |
| 22:16 | • Reply: How can I check if a database is valid? artifact: 9aa101f90e user: kmedcalf | |
| 21:53 | • Reply: Research questions about how sqlite works artifact: 58d988b909 user: kmedcalf | |
| 21:50 | • Reply: Research questions about how sqlite works artifact: f3c3b4c8b8 user: kmedcalf | |
| 21:43 | • Reply: Research questions about how sqlite works artifact: 0e9daee70b user: pepijnve | |
| 21:35 | • Reply: How can I check if a database is valid? artifact: ff572b024f user: kmedcalf | |
| 21:30 | • Reply: How can I check if a database is valid? artifact: 43d51dbd6a user: larrybr | |
| 21:22 | • Reply: How can I check if a database is valid? artifact: aff810fbaa user: phil_g | |
| 21:00 | • Post: How can I check if a database is valid? artifact: da8f30ee2b user: LcccXmm | |
| 19:45 | • Reply: Comments in column names artifact: 9f4708e167 user: larrybr | |
| 19:41 | • Edit reply: Comments in column names artifact: 9b3f253681 user: stephan | |
| 19:40 | • Reply: Comments in column names artifact: c8c901b11c user: stephan | |
| 19:39 | • Reply: Comments in column names artifact: 9ed8af70a1 user: AAsk1902 | |
| 19:05 | • Reply: Comments in column names artifact: c393913df5 user: larrybr | |
| 18:42 | • Edit reply: Comments in column names artifact: a9b5fe2f4e user: AAsk1902 | |
| 18:39 | • Reply: Comments in column names artifact: 731c53dc9a user: AAsk1902 | |
| 18:18 | • Reply: SQlite encryption artifact: c012f88ed1 user: kmedcalf | |
| 18:14 | • Reply: SQlite encryption artifact: 007a14e8db user: anonymous | |
| 17:44 | • Reply: Comments in column names artifact: b3fdae8f70 user: anonymous | |
| 17:43 | • Reply: SQlite encryption artifact: 9c55bba063 user: anonymous | |
| 17:01 | • Reply: Comments in column names artifact: 488549a0a4 user: larrybr | |
| 16:17 | • Post: Comments in column names artifact: 9887889369 user: anonymous | |
| 16:16 | • Reply: Hooks invoked when modifications done from another connection? artifact: 325f18a086 user: kmedcalf | |
| 16:09 | • Edit reply: DLL load failed %1 is not a valid Win32 application artifact: 8d7158476e user: kmedcalf | |
| 15:58 | • Reply: DLL load failed %1 is not a valid Win32 application artifact: ba358a14ca user: kmedcalf | |
| 15:45 | • Reply: DLL load failed %1 is not a valid Win32 application artifact: b7fc30333c user: kmedcalf | |
| 15:31 | • Reply: Research questions about how sqlite works artifact: e61b035e32 user: kmedcalf | |
| 15:21 | • Reply: Hooks invoked when modifications done from another connection? artifact: 2a15c79b36 user: bjmgeek | |
| 15:16 | • Reply: DLL load failed %1 is not a valid Win32 application artifact: 1d221b52c7 user: wkwkwk | |
| 15:16 | • Edit reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: a08e8829bd user: kmedcalf | |
| 15:08 | • Reply: Release history typo artifact: 3aa7ec7aec user: drh | |
| 15:07 | • Edit reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 4075e79187 user: kmedcalf | |
| 15:07 | • Reply: Release history typo artifact: 811e14ce5c user: jicman | |
| 15:06 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 9d3e492e83 user: kmedcalf | |
| 15:03 | • Reply: Release history typo artifact: bc62ce4458 user: rogerbinns | |
| 14:59 | • Post: Release history typo artifact: c817321127 user: dvdraymond | |
| 14:50 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: c67b95b9b0 user: ddevienne | |
| 14:48 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 2b2261f5b2 user: ddevienne | |
| 14:47 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 2c9738ca7d user: kmedcalf | |
| 14:43 | • Edit reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 65392699a2 user: kmedcalf | |
| 14:42 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 4a1a2f45d3 user: kmedcalf | |
| 14:37 | • Edit reply: Research questions about how sqlite works artifact: eab3008138 user: pepijnve | |
| 14:35 | • Edit reply: Research questions about how sqlite works artifact: 86404b33f7 user: pepijnve | |
| 14:34 | • Edit reply: Research questions about how sqlite works artifact: a219f2e62d user: pepijnve | |
| 14:31 | • Reply: Research questions about how sqlite works artifact: bd127b8082 user: pepijnve | |
| 14:27 | • Reply: Research questions about how sqlite works artifact: 9a4caa0d76 user: kmedcalf | |
| 14:12 | • Reply: DLL load failed %1 is not a valid Win32 application artifact: 97f323354c user: kmedcalf | |
| 12:28 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 8abc5168f6 user: bjoern | |
| 12:16 | • Reply: Research questions about how sqlite works artifact: bc53a19b78 user: pepijnve | |
| 11:42 | • Reply: WHERE queries matchang Type failing since 3.41.0 artifact: 71dfab884b user: h2sbf7aq | |
| 11:40 | • Reply: WHERE queries matchang Type failing since 3.41.0 artifact: fc829614d8 user: drh | |
| 11:34 | • Reply: WHERE queries matchang Type failing since 3.41.0 artifact: 0487e96049 user: stephan | |
| 11:33 | • Edit: WHERE queries matchang Type failing since 3.41.0 artifact: fd191a38ea user: h2sbf7aq | |
| 11:32 | • Post: WHERE queries matchang Type failing since 3.41.0 artifact: 657ce6623a user: h2sbf7aq | |
| 05:29 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 40bdd782c3 user: 1codedebugger | |
| 04:38 | • Edit reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 85ce89625b user: kmedcalf | |
| 04:34 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 9f1f4a8331 user: kmedcalf | |
| 04:33 | • Reply: DLL load failed %1 is not a valid Win32 application artifact: 186c5f04a8 user: wkwkwk | |
| 04:26 | • Reply: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 0352f3b842 user: kmedcalf | |
| 03:18 | • Post: What am I doing wrong to cause the table scan order in query plans to differ? artifact: 6932395e4a user: 1codedebugger | |
| 02:24 | • Reply: Inconsistent results when enable/disable OmitOrderBy optimization artifact: 82d27056fa user: songliu | |
| 01:28 | • Reply: Inconsistent results when enable/disable OmitOrderBy optimization artifact: 7bb7660871 user: larrybr | |
| 00:59 | • Post: Inconsistent results when enable/disable OmitOrderBy optimization artifact: 44c287d1bc user: songliu | |
2 Years Ago (more context)
|
2022-03-22
| ||
| 14:58 | • Reply: Write locking and subqueries artifact: 96b95ea0b6 user: anonymous | |
| 14:43 | • Reply: Write locking and subqueries artifact: e46eb2a195 user: sqweek | |
| 14:38 | • Reply: How to modify languageid column in FTS table artifact: e3740ed0fd user: anonymous | |
| 14:20 | • Reply: Write locking and subqueries artifact: 73237ae513 user: drh | |
| 14:16 | • Reply: Write locking and subqueries artifact: 4afbbedf94 user: larrybr | |
| 13:57 | • Reply: Write locking and subqueries artifact: 1697a61961 user: anonymous | |
| 13:51 | • Reply: Write locking and subqueries artifact: 0c26452a6c user: drh | |
| 13:01 | • Reply: Just curious: Bytecode generation - non SQL input? artifact: 9572396913 user: gunter_hick | |
| 13:00 | • Reply: how to set output mode in tcl script via sqlite3 driver artifact: 6e582a0d5e user: dkfellows | |
| 12:46 | • Post: Write locking and subqueries artifact: e10bd33bcf user: anonymous | |
| 12:23 | • Reply: how to set output mode in tcl script via sqlite3 driver artifact: 8a1b17a665 user: jarod.tian | |
| 12:16 | • Reply: how to set output mode in tcl script via sqlite3 driver artifact: 26bc1a0d46 user: jarod.tian | |
| 10:25 | • Reply: how to set output mode in tcl script via sqlite3 driver artifact: a70c3c24a5 user: drh | |
| 10:14 | • Reply: how to set output mode in tcl script via sqlite3 driver artifact: 1ef219d708 user: stephan | |
| 07:55 | • Post: how to set output mode in tcl script via sqlite3 driver artifact: 9f5f2b3284 user: jarod.tian | |
| 07:32 | • Post: How to modify languageid column in FTS table artifact: 17fe098921 user: anonymous | |
| 03:17 | • Reply: Just curious: Bytecode generation - non SQL input? artifact: cfdd7ea16d user: deonb | |
| 00:23 | • Reply: Mac ARM binaries on download page? artifact: 986b6cd136 user: widdowson | |
3 Years Ago (more context)
|
2021-03-22
| ||
| 23:55 | • Edit reply: Strange CLI .exit issue artifact: f0913e5e39 user: kmedcalf | |
| 23:55 | • Reply: Strange CLI .exit issue artifact: cfa5258799 user: kmedcalf | |
| 23:43 | • Reply: Strange CLI .exit issue artifact: 51dc89703e user: kmedcalf | |
| 23:41 | • Reply: Strange CLI .exit issue artifact: d1e963806d user: kmedcalf | |
| 23:37 | • Reply: Strange CLI .exit issue artifact: c053d0a861 user: kmedcalf | |
| 23:32 | • Reply: Strange CLI .exit issue artifact: 937b1c01bf user: kmedcalf | |
| 23:06 | • Reply: Strange CLI .exit issue artifact: 68f7382be7 user: larrybr | |
| 21:43 | • Reply: DROP TABLE failure - is it intentional or a bug? artifact: 1af825eb37 user: kmedcalf | |
| 21:06 | • Reply: Strange CLI .exit issue artifact: d29be8e88d user: anonymous | |
| 21:05 | • Post: DROP TABLE failure - is it intentional or a bug? artifact: 814a51ba88 user: younique | |
| 20:17 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: 7a3ab9806d user: dan | |
| 19:56 | • Post: incremental_vacuum and WAL size artifact: bca9f3906a user: abarr5 | |
| 19:32 | • Reply: Looking for the documentation drawing artifact: 47698cb579 user: test228 | |
| 19:29 | • Reply: Looking for the documentation drawing artifact: e061bbee67 user: stephan | |
| 19:20 | • Post: Looking for the documentation drawing artifact: eb8247cace user: test228 | |
| 14:54 | • Reply: HTML login/registration with SQLite db table artifact: f3b3f561c6 user: Trudge | |
| 12:58 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: bc267ed84c user: mzm2021 | |
| 12:40 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: 60ce420d42 user: drh | |
| 12:28 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: ef1b233ef3 user: mzm2021 | |
| 12:09 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: 16c9a950ae user: drh | |
| 09:45 | • Reply: Bug report: Complex CTE generates segmentation fault depending on the order of joined tables in its body artifact: 1f75ed5db7 user: mzm2021 | |
| 01:39 | • Edit reply: When is SELECT ... FROM with no table-or-subquery valid. artifact: 7985095fbb user: larrybr | |
| 01:32 | • Reply: Building testfixture for Windows on Linux using mingw artifact: d2f6c45303 user: anonymous | |
| 00:31 | • Reply: php error : SQLSTATEHY000: General error: 6 database table is locked artifact: df9fa762a3 user: stephan | |
| 00:08 | • Reply: php error : SQLSTATEHY000: General error: 6 database table is locked artifact: b36d5a3d59 user: larrybr | |
4 Years Ago (more context)
|
2020-03-22
| ||
| 20:23 | • Reply: Reading/writing record format artifact: bf9334821a user: kmedcalf | |
| 16:37 | • Reply: Reading/writing record format artifact: bf52eddf49 user: anonymous | |
| 15:14 | • Reply: Help:Could I use SQLite in-memory database with WAL mode? artifact: a44bddd657 user: kmedcalf | |
| 12:21 | • Reply: Feature Request: Option to store sqlite db in plain text format (e.g. csv) artifact: 6acf7e6168 user: drh | |
| 12:17 | • Post: Help:Could I use SQLite in-memory database with WAL mode? artifact: 403134ee7a user: xxk | |
| 12:07 | • Reply: Feature Request: Option to store sqlite db in plain text format (e.g. csv) artifact: 9960d82ee7 user: anonymous | |
| 11:29 | • Reply: Reading/writing record format artifact: 5d3d17906a user: drh | |
| 11:21 | • Reply: Reading/writing record format artifact: 1008fda758 user: drh | |
| 11:06 | • Reply: Feature Request: Option to store sqlite db in plain text format (e.g. csv) artifact: f0af7ad6c8 user: stephan | |
| 10:59 | • Post: Feature Request: Option to store sqlite db in plain text format (e.g. csv) artifact: c7b667aa9d user: anonymous | |
| 05:14 | • Reply: Request for comment: New ANALYZE syntax artifact: f12444df65 user: anonymous | |
| 05:10 | • Reply: Reading/writing record format artifact: e108bf55b2 user: stephan | |
| 05:02 | • Reply: Reading/writing record format artifact: 358a58045a user: anonymous | |
| 04:47 | • Reply: Is SQLite support JSON_VALUE function of SQL Server? artifact: 9119ab89e0 user: anonymous | |
| 04:46 | • Reply: Reading/writing record format artifact: b30b242f3c user: stephan | |
| 04:30 | • Reply: Reading/writing record format artifact: 01a3cd54e4 user: anonymous | |
| 03:20 | • Reply: Is SQLite support JSON_VALUE function of SQL Server? artifact: 9af507ce0b user: wyoung | |