This Day In History For 2024-04-21
1 Year Ago (more context)
|
2023-04-21
| ||
| 20:01 | • Reply: Re-Direct SQLite temp files to another directory artifact: 7aa3a271f7 user: jicman | |
| 19:43 | • Reply: Re-Direct SQLite temp files to another directory artifact: 85e55097df user: jbart1112 | |
| 18:53 | • Reply: comparing (dis)advantages of ATTACHED vs all-in-one db artifact: 65a1979efc user: drh | |
| 18:45 | • Reply: comparing (dis)advantages of ATTACHED vs all-in-one db artifact: d0443f5a6a user: Clothears | |
| 18:25 | • Reply: Re-Direct SQLite temp files to another directory artifact: f2acba9eda user: jbart1112 | |
| 17:19 | • Reply: Feature request: unixepoch_ms() for Unix timestamp in milliseconds artifact: 164c5a9609 user: kmedcalf | |
| 16:10 | • Reply: Re-Direct SQLite temp files to another directory artifact: 1bc108ca5e user: larrybr | |
| 16:05 | • Reply: Re-Direct SQLite temp files to another directory artifact: a8ee4d455f user: jicman | |
| 15:57 | • Reply: Single-thread Mode artifact: ba0387ee75 user: larrybr | |
| 15:46 | • Reply: Feature request: unixepoch_ms() for Unix timestamp in milliseconds artifact: 867adfcdbd user: drh | |
| 15:38 | • Post: Re-Direct SQLite temp files to another directory artifact: 81e88291d9 user: jbart1112 | |
| 15:38 | • Reply: test_syscall.c: ts_read function signature incorrect artifact: 42d1f668ff user: stephan | |
| 14:14 | • Post: test_syscall.c: ts_read function signature incorrect artifact: 947169d5e7 user: 0xjnml | |
| 13:30 | • Reply: Single-thread Mode artifact: f0eb2fef72 user: dkfellows | |
| 12:04 | • Reply: A possible resource leak in shell.c artifact: bdcbed0e12 user: AAsk1902 | |
| 11:34 | • Reply: A possible resource leak in shell.c artifact: 09f3bdc464 user: jicman | |
| 11:25 | • Reply: A possible resource leak in shell.c artifact: 2bd11fbf3d user: drh | |
| 11:19 | • Reply: A possible resource leak in shell.c artifact: 1254973691 user: larrybr | |
| 11:08 | • Reply: A possible resource leak in shell.c artifact: a177e56a0d user: AAsk1902 | |
| 10:16 | • Reply: comparing (dis)advantages of ATTACHED vs all-in-one db artifact: 24b463981f user: Eduardo | |
| 10:02 | • Reply: A possible resource leak in shell.c artifact: 6fc634e91a user: larrybr | |
| 09:55 | • Reply: SQLite on a Server artifact: d26eb09bc5 user: Eduardo | |
| 09:43 | • Post: A possible resource leak in shell.c artifact: 20aaf01123 user: lappland | |
2 Years Ago (more context)
|
2022-04-21
| ||
| 22:48 | • Edit reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 34f2e63771 user: kmedcalf | |
| 22:47 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: de7bc72caf user: kmedcalf | |
| 22:35 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 81dc1cb345 user: kmedcalf | |
| 22:23 | • Edit reply: GUI with drill-down? artifact: af24cf6aba user: AAsk1902 | |
| 22:17 | • Reply: GUI with drill-down? artifact: d24a1fa72d user: AAsk1902 | |
| 21:20 | • Reply: USING Clause on Full Outer Join Gives Nulls? artifact: 5c817a8b6f user: SeverKetor | |
| 21:19 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: f31b380839 user: lukas.eder | |
| 21:08 | • Edit reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 098db2b213 user: lukas.eder | |
| 21:08 | • Edit reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 089e889602 user: lukas.eder | |
| 21:06 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 77d2a753ea user: lukas.eder | |
| 20:53 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: e73205b553 user: lukas.eder | |
| 20:14 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: ef5d1b07e5 user: cuz | |
| 19:44 | • Reply: USING Clause on Full Outer Join Gives Nulls? artifact: c19d6da9fb user: drh | |
| 19:15 | • Edit reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: dd216113b4 user: lukas.eder | |
| 19:15 | • Edit reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: ceac5fc2fd user: lukas.eder | |
| 19:13 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 52eb11ca20 user: lukas.eder | |
| 19:09 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: fbfc0f458f user: lukas.eder | |
| 16:25 | • Reply: GUI with drill-down? artifact: 7e858c769f user: UserMBL | |
| 16:15 | • Reply: GUI with drill-down? artifact: a1fe8d04c0 user: JrgMyr | |
| 16:14 | • Reply: GUI with drill-down? artifact: be5baf6640 user: JrgMyr | |
| 16:03 | • Reply: Surprising behavior of aggregate JSON functions? artifact: ba160cf2fe user: loveencounterflow | |
| 15:45 | • Reply: GUI with drill-down? artifact: 31e4ba1456 user: skywalk | |
| 15:45 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: dffb8aeae9 user: cuz | |
| 15:21 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 130d6a5e85 user: mingodad | |
| 14:22 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 7e920ebae6 user: larrybr | |
| 13:53 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: cdd773cd2a user: lukas.eder | |
| 13:41 | • Reply: Sqllogictest question artifact: 827809afd0 user: bucweat | |
| 13:39 | • Reply: Sqllogictest question artifact: 6b4d6bfaa8 user: anonymous | |
| 13:35 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: a116917be9 user: dvdraymond | |
| 13:32 | • Reply: send blob with sendfile() artifact: c4728efe1c user: larrybr | |
| 13:23 | • Reply: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: 16fcd671e2 user: dvdraymond | |
| 12:24 | • Post: send blob with sendfile() artifact: d8135db8fb user: anonymous | |
| 12:19 | • Post: Parser bug in INSERT .. SELECT .. ON CONFLICT clause artifact: d03b7325bd user: lukas.eder | |
| 09:34 | • Reply: GUI with drill-down? artifact: 2b6bbc2c05 user: AAsk1902 | |
| 09:19 | • Reply: GUI with drill-down? artifact: 7e0f4b23c4 user: stephan | |
| 09:06 | • Post: GUI with drill-down? artifact: e4472f0d9d user: JrgMyr | |
| 02:51 | • Reply: VS, C# SQLite Interop files artifact: b7f5704e3b user: eKundl | |
3 Years Ago (more context)
|
2021-04-21
| ||
| 22:03 | • Reply: Will there be a 64-bit Windows Download for v3.35.5? artifact: f1a4f529ef user: larrybr | |
| 20:00 | • Reply: V 3.35.5 artifact: 48d7e880d3 user: larrybr | |
| 19:08 | • Reply: V 3.35.5 artifact: aa005429ab user: anonymous | |
| 18:01 | • Reply: Bug report: inconsistent error message across different CONSTRAINT types artifact: d18481bf50 user: warmwaffles | |
| 17:38 | • Reply: query plan for "is null" on column defined as "not null" artifact: fd9662783e user: drh | |
| 17:01 | • Post: query plan for "is null" on column defined as "not null" artifact: 85be5cc08f user: anonymous | |
| 17:00 | • Reply: The NUMERIC data type? artifact: c3b826e9c3 user: wyoung | |
| 16:49 | • Post: query plan for "is null" on column defined as "not null" artifact: dc6fcfe6b2 user: anonymous | |
| 14:45 | • Reply: Should tables be populated based upon a known/expected pattern of retrieval? artifact: a51549f0b6 user: cuz | |
| 14:18 | • Reply: Should tables be populated based upon a known/expected pattern of retrieval? artifact: 0df88dcda0 user: cuz | |
| 13:52 | • Reply: The NUMERIC data type? artifact: 437810a956 user: ddevienne | |
| 12:41 | • Reply: Why no release announcement in this Forum anymore? artifact: 1778ca6fb1 user: knu | |
| 12:40 | • Reply: The NUMERIC data type? artifact: 0b84318a48 user: holgerj | |
| 12:26 | • Edit reply: The NUMERIC data type? artifact: 06e0deed61 user: slavin | |
| 12:22 | • Reply: The NUMERIC data type? artifact: c952a6ff34 user: slavin | |
| 07:52 | • Reply: The NUMERIC data type? artifact: 7b065ccf40 user: anonymous | |
| 07:20 | • Edit reply: Why no release announcement in this Forum anymore? artifact: fa3a6af85b user: ddevienne | |
| 07:19 | • Reply: Why no release announcement in this Forum anymore? artifact: db976e5c4d user: ddevienne | |
| 04:16 | • Post: Should tables be populated based upon a known/expected pattern of retrieval? artifact: eae63cb9d6 user: 1codedebugger | |
| 04:11 | • Reply: Will there be a 64-bit Windows Download for v3.35.5? artifact: 23bbb607e8 user: anonymous | |
| 03:39 | • Reply: Will there be a 64-bit Windows Download for v3.35.5? artifact: 8c8182630d user: larrybr | |
| 03:37 | • Reply: How to compile the libsqlitejdbc.so? artifact: c81316c902 user: larrybr | |
| 03:27 | • Reply: Will there be a 64-bit Windows Download for v3.35.5? artifact: d45bbb5fe0 user: anonymous | |
| 03:20 | • Post: How to compile the libsqlitejdbc.so? artifact: 5d7b069676 user: anonymous | |
| 02:37 | • Edit reply: The NUMERIC data type? artifact: 6c939f8f70 user: kmedcalf | |
| 02:29 | • Edit reply: The NUMERIC data type? artifact: 44aca9a5a8 user: kmedcalf | |
| 02:29 | • Reply: The NUMERIC data type? artifact: 0e6ea27a93 user: kmedcalf | |
| 02:04 | • Post: Will there be a 64-bit Windows Download for v3.35.5? artifact: 3080f97941 user: anonymous | |
| 01:09 | • Post: The NUMERIC data type? artifact: 6540c75cf6 user: anonymous | |
4 Years Ago (more context)
|
2020-04-21
| ||
| 21:35 | • Reply: How do create the neat flow diagrams for SQLite? artifact: 8c42451029 user: wyoung | |
| 21:27 | • Post: Feature request: ORDER BY with non-window aggregate functions artifact: a33d8dac09 user: anonymous | |
| 21:18 | • Reply: How do create the neat flow diagrams for SQLite? artifact: 694f591385 user: doug9forester | |
| 20:08 | • Reply: How do create the neat flow diagrams for SQLite? artifact: 7d0b1bdbe8 user: LarryBrasfield | |
| 19:56 | • Reply: How do create the neat flow diagrams for SQLite? artifact: ac26fc679f user: wyoung | |
| 19:40 | • Reply: Show number with thousands separator artifact: b5a6fa11c7 user: anonymous | |
| 19:31 | • Reply: Show number with thousands separator artifact: edd644208c user: drh | |
| 19:20 | • Post: Show number with thousands separator artifact: 3e25dd3776 user: anonymous | |
| 18:54 | • Reply: How do create the neat flow diagrams for SQLite? artifact: 4c8819a3e8 user: doug9forester | |
| 17:52 | • Reply: How do create the neat flow diagrams for SQLite? artifact: f2c72f0140 user: wyoung | |
| 16:58 | • Reply: How do create the neat flow diagrams for SQLite? artifact: 8bbd4f5ec5 user: doug9forester | |
| 16:56 | • Reply: tcl / db eval error artifact: 25d05b8f2a user: GSnyder | |
| 16:22 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: a92e0fef9b user: dvdraymond | |
| 16:14 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: a5d8b7b733 user: kmedcalf | |
| 15:59 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: 88ad9a7c70 user: ddevienne | |
| 15:57 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: a54a3b8dbc user: ddevienne | |
| 15:49 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: 940d6ca813 user: ddevienne | |
| 15:04 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: cef68d511e user: kmedcalf | |
| 14:48 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: dcba8698b2 user: drh | |
| 14:30 | • Reply: sqlite3.exe export with bom artifact: 276ffbb8e6 user: LarryBrasfield | |
| 14:25 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: 939084cade user: rwillett | |
| 13:22 | • Reply: sqlite3.exe export with bom artifact: 07465439c3 user: neubauer | |
| 12:14 | • Reply: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: 8705c0879b user: gunter_hick | |
| 11:27 | • Post: Country-coding from Lat/Long, using GeoPoly and/or R-Tree artifact: c20e74b1dc user: ddevienne | |
| 09:50 | • Reply: sqlite3.exe export with bom artifact: 919aa988de user: neubauer | |
| 09:30 | • Post: tcl / db eval error artifact: 5ab1340735 user: anonymous | |
| 01:33 | • Reply: Typo in "The LIKE Optimization" docs artifact: d81308600c user: drh | |