This Day In History For 2025-10-17
1 Year Ago (more context)
2024-10-17
| ||
19:05 | • Reply: Same column miultiple times in an INSERT artifact: 0554a85fa9 user: rogerbinns | |
18:49 | • Reply: Same column miultiple times in an INSERT artifact: 9b77a4615b user: drh | |
18:03 | • Reply: Help understanding the effect of BEGIN IMMEDIATE artifact: 04ed1d235b user: rhcarvalho | |
17:02 | • Reply: Help understanding the effect of BEGIN IMMEDIATE artifact: 30a8ec24b4 user: rhcarvalho | |
15:45 | • Reply: Same column miultiple times in an INSERT artifact: f684e894dd user: rogerbinns | |
13:33 | • Post: Same column miultiple times in an INSERT artifact: 9a93fe39d9 user: rogerbinns | |
12:35 | • Reply: Possible regression for read-only databases in 3.46.1 (WASM) artifact: 245a521493 user: stephan | |
11:45 | • Edit reply: Possible regression for read-only databases in 3.46.1 (WASM) artifact: 1e8cb7c02a user: stephan | |
11:42 | • Reply: sqlite wasm custom builds artifact: 2fc3b62224 user: stephan | |
10:48 | • Reply: sqlite wasm custom builds artifact: 619df15832 user: FakeUser | |
10:24 | • Reply: sqlite wasm custom builds artifact: ea81a1cd0e user: stephan | |
10:08 | • Post: sqlite wasm custom builds artifact: cebd91c015 user: FakeUser | |
09:50 | • Reply: Possible regression for read-only databases in 3.46.1 (WASM) artifact: 05dcc26ad0 user: stephan | |
03:58 | • Post: Possible regression for read-only databases in 3.46.1 (WASM) artifact: cf37d5ff11 user: DallasHoff | |
2 Years Ago (more context)
2023-10-17
| ||
22:49 | • Reply: SQLITE_ENABLE_UPDATE_DELETE_LIMIT might make WHERE mandatory before RETURNING in UPDATE artifact: 94d63d8328 user: drh | |
22:12 | • Reply: SQLITE_ENABLE_UPDATE_DELETE_LIMIT might make WHERE mandatory before RETURNING in UPDATE artifact: 52cc503296 user: larrybr | |
17:07 | • Reply: Fix FAQ Entry for #5 artifact: 87f14dd4b7 user: Clothears | |
16:47 | • Reply: Fix FAQ Entry for #5 artifact: 78f082a60d user: larrybr | |
15:28 | • Reply: Fix FAQ Entry for #5 artifact: e2ecd36bc6 user: SeverKetor | |
14:20 | • Reply: Storage of internal B-tree artifact: d36d0f61d9 user: ddevienne | |
14:09 | • Post: Fix FAQ Entry for #5 artifact: b034385515 user: EvanCarroll | |
13:59 | • Reply: Storage of internal B-tree artifact: d13e402318 user: drh | |
13:54 | • Reply: json_set bug (3.43.2) artifact: 487ddeb481 user: drh | |
13:47 | • Reply: Storage of internal B-tree artifact: f8fb232e91 user: ddevienne | |
13:26 | • Reply: Crazy Idea: SQLite-based HTTP Application Server That Make SQL Injection Impossible artifact: aad2e92dc3 user: dkfellows | |
12:41 | • Reply: Crazy Idea: SQLite-based HTTP Application Server That Make SQL Injection Impossible artifact: 485bdd552f user: anonymous | |
12:35 | • Reply: Storage of internal B-tree artifact: c3d9364f08 user: dvdraymond | |
12:10 | • Post: json_set bug (3.43.2) artifact: fc0e3f1e2a user: UnderKoen | |
08:02 | • Reply: Storage of internal B-tree artifact: 5ca00c3d2f user: ddevienne | |
07:48 | • Reply: Crazy Idea: SQLite-based HTTP Application Server That Make SQL Injection Impossible artifact: 65218c2985 user: ddevienne | |
07:43 | • Reply: Crazy Idea: SQLite-based HTTP Application Server That Make SQL Injection Impossible artifact: 5f000ee5d2 user: ddevienne | |
07:12 | • Reply: Differences between two database? artifact: 54db92ca67 user: Mucipp | |
06:55 | • Reply: Differences between two database? artifact: 40a96a3162 user: wyoung | |
06:40 | • Post: Differences between two database? artifact: 3a0e021a10 user: Mucipp | |
03:51 | • Post: SQLITE_ENABLE_UPDATE_DELETE_LIMIT might make WHERE mandatory before RETURNING in UPDATE artifact: d8f57775be user: anonymous | |
02:26 | • Edit: Android 9 crash artifact: 84e844b88b user: foolishgao | |
02:22 | • Post: Android 9 crash artifact: f9e184b6d3 user: foolishgao | |
01:31 | • Reply: sqlite3_deserialize returning 'unable to open database file' artifact: ae5dca4eaa user: stephan | |
01:15 | • Reply: sqlite3_deserialize returning 'unable to open database file' artifact: 6a03a1aaaf user: fmzakari | |
3 Years Ago (more context)
2022-10-17
| ||
22:51 | • Post: Case insensitivity not applied while coalescing artifact: 00de131281 user: amjith | |
20:21 | • Reply: Clarification on VACUUMing artifact: 79adb03b01 user: wyoung | |
20:06 | • Reply: Sqlite3 crashed artifact: 102d58ba96 user: chrisjlocke1 | |
18:14 | • Reply: Clarification on VACUUMing artifact: 77c2ccd879 user: adrian | |
18:04 | • Reply: Segmentation Fault on query artifact: e63670d8a1 user: anonymous | |
18:02 | • Edit reply: sqlite3_update_hook - which changes are consiered? artifact: 3eb7712cb8 user: stephan | |
17:50 | • Reply: sqlite3_update_hook - which changes are consiered? artifact: 654890e0ed user: jtheisen42 | |
17:24 | • Reply: Segmentation Fault on query artifact: 2784455287 user: LY1598773890 | |
17:23 | • Edit: Possible CLI crashing bug artifact: 142b868da7 user: LY1598773890 | |
17:23 | • Post: Possible CLI crashing bug artifact: 25df3b9314 user: LY1598773890 | |
17:20 | • Reply: Identify a transaction in a trigger artifact: 5746c84cd0 user: berzerker | |
17:20 | • Reply: soliciting ideas on how to store and query XMLs artifact: 7b0015350a user: jicman | |
16:28 | • Reply: "UNIQUE constraint failed" error with UPSERT and UPDATE trigger that does INSERT OR REPLACE artifact: c8fddc5cd4 user: drh | |
16:28 | • Reply: Does the design of deferred transactions lead to deadlocks? artifact: e19cdb8868 user: anonymous | |
16:17 | • Reply: Segmentation Fault on query artifact: e71aeb3c06 user: drh | |
16:07 | • Reply: Segmentation Fault on query artifact: 592fa79a07 user: RandomCoder | |
15:52 | • Edit: Segmentation Fault on query artifact: 2d5cea0a2c user: LY1598773890 | |
15:47 | • Edit: Segmentation Fault on query artifact: a932630dce user: LY1598773890 | |
15:45 | • Post: soliciting ideas on how to store and query XMLs artifact: 2df51eaf93 user: punkish | |
15:43 | • Post: Clarification on VACUUMing artifact: 49b7e2a422 user: adrian | |
15:42 | • Post: Segmentation Fault on query artifact: 9c4f2ebe22 user: LY1598773890 | |
15:33 | • Reply: Generate SHA for a table artifact: ad0566b93e user: kmedcalf | |
14:45 | • Reply: Identify a transaction in a trigger artifact: c066a77fe3 user: dvdraymond | |
13:54 | • Reply: Identify a transaction in a trigger artifact: ab89ed5c1f user: berzerker | |
13:03 | • Reply: GUI with drill-down? artifact: f16e0c164e user: SunnySaini_com | |
13:01 | • Reply: Generate SHA for a table artifact: 9c4aae45c6 user: gunter_hick | |
13:00 | • Reply: Generate SHA for a table artifact: 7efd278063 user: drh | |
12:46 | • Reply: Generate SHA for a table artifact: 529ca2f7df user: adrian | |
12:42 | • Reply: Generate SHA for a table artifact: 6f4bfe7903 user: adrian | |
12:35 | • Reply: Generate SHA for a table artifact: d4653edb2f user: adrian | |
12:27 | • Reply: Generate SHA for a table artifact: d72d282cf7 user: SunnySaini_com | |
12:21 | • Reply: Some peeks in execution time artifact: 858b426d83 user: slavin | |
12:12 | • Post: Sqlite3 crashed artifact: 222dde45cd user: AsadCoder | |
09:52 | • Reply: Identify a transaction in a trigger artifact: 2421eaf698 user: dkfellows | |
07:23 | • Reply: Split db into smaller dbs artifact: f1bfffd9c1 user: ddevienne | |
07:21 | • Reply: Generate SHA for a table artifact: 6ef40d48be user: ddevienne | |
4 Years Ago (more context)
2021-10-17
| ||
22:29 | • Post: Column names and aliases in expressions artifact: 3e8144ee2b user: anacrolix | |
5 Years Ago (more context)
2020-10-17
| ||
22:50 | • Reply: The sqlite3_deserialize comment and behavior do not coincide artifact: 5e0d020c15 user: drh | |
20:36 | • Post: The sqlite3_deserialize comment and behavior do not coincide artifact: ba1dff667a user: holybrake | |
19:00 | • Reply: SQLite encryption with SEE artifact: c4ebce7b47 user: aloys | |
17:37 | • Post: src/where.c: bad printf format artifact: 80a9c47769 user: penguin42 | |
07:58 | • Reply: SQLite encryption with SEE artifact: 81d13c7fac user: nbevans | |