This Day In History For 2025-06-02
1 Year Ago (more context)
2024-06-02
| ||
20:45 | • Reply: Handling of empty, zero-length files artifact: 2ec68b114e user: _blgl_ | |
19:44 | • Reply: UPDATE multiple values in column FROM JSON object artifact: cd4053c5a4 user: punkish | |
18:53 | • Reply: Handling of empty, zero-length files artifact: 727163771f user: utelle | |
16:06 | • Reply: An UPDATE trigger is not fired for the REPLACE statement. artifact: fcf2796750 user: PChemGuy | |
15:21 | • Reply: An UPDATE trigger is not fired for the REPLACE statement. artifact: cb6a4f3e6c user: _blgl_ | |
15:03 | • Post: An UPDATE trigger is not fired for the REPLACE statement. artifact: e8332908cb user: PChemGuy | |
13:48 | • Reply: Detect/reject CREATE/DROP/ALTER DML queries artifact: e3a895d097 user: PChemGuy | |
13:07 | • Reply: Detect/reject CREATE/DROP/ALTER DML queries artifact: ef38231e82 user: _blgl_ | |
13:03 | • Post: Detect/reject CREATE/DROP/ALTER DML queries artifact: 265ab98be2 user: PChemGuy | |
10:32 | • Edit reply: Can we use SQLite wasm directly from c-interface instead of javascript files artifact: 6440f6824d user: ncruces | |
10:07 | • Post: JSON library output stability artifact: b616ffecd1 user: PChemGuy | |
09:44 | • Reply: C Functions for BEGIN and END transaction artifact: e41e25724a user: _blgl_ | |
09:16 | • Reply: CAST AS NUMERIC returns REAL for a float apparently convertible o an integer artifact: 969cac6950 user: _blgl_ | |
09:03 | • Reply: Can we use SQLite wasm directly from c-interface instead of javascript files artifact: 7446d91466 user: stephan | |
07:21 | • Reply: Handling of empty, zero-length files artifact: b0e26963e8 user: spindrift | |
06:54 | • Edit: Inconsistent docs for the ->> operator artifact: 9f2fdc0717 user: PChemGuy | |
06:19 | • Edit: CAST AS NUMERIC returns REAL for a float apparently convertible o an integer artifact: 8caf94e4ca user: PChemGuy | |
06:19 | • Post: CAST AS NUMERIC returns REAL for a float apparently convertible o an integer artifact: 1b901f7c1a user: PChemGuy | |
05:52 | • Post: Inconsistent docs for the ->> operator artifact: 3cfde72cad user: PChemGuy | |
04:08 | • Reply: Handling of empty, zero-length files artifact: d3cc72104f user: codehz | |
01:33 | • Reply: Handling of empty, zero-length files artifact: 172a5ea91d user: sqlitening | |
00:56 | • Reply: Handling of empty, zero-length files artifact: 747ac5be8f user: rogerbinns | |
00:06 | • Reply: C Functions for BEGIN and END transaction artifact: d0feb89162 user: vman59 | |
2 Years Ago (more context)
2023-06-02
| ||
22:24 | • Edit reply: Suggestion: JSON support artifact: 5a166735ce user: larrybr | |
22:07 | • Reply: Suggestion: JSON support artifact: b6dfbb854e user: larrybr | |
21:52 | • Post: Suggestion: JSON support artifact: cfe7bae7b0 user: jckodel | |
21:44 | • Reply: SQLite3 Interruption artifact: c3813a3c88 user: larrybr | |
20:53 | • Post: SQLite3 Interruption artifact: 8fa7a9e81b user: AAsk1902 | |
20:37 | • Reply: sqlite fts4 offsets data with diacritics Latin characters artifact: b548f73ac4 user: anonymous | |
19:36 | • Post: sqlite fts4 offsets data with diacritics Latin characters artifact: 3cc32e806b user: oduconge | |
18:58 | • Reply: How is a count(*) index decided? artifact: 92782b1e29 user: deonb | |
17:06 | • Edit reply: Feature Request: shell prompt for query parameters artifact: 392fff85f4 user: larrybr | |
16:54 | • Reply: Feature Request: shell prompt for query parameters artifact: 9c4d1c60fa user: larrybr | |
16:38 | • Delete reply: Feature Request: shell prompt for query parameters artifact: a829946c43 user: AAsk1902 | |
16:36 | • Reply: Feature Request: shell prompt for query parameters artifact: 54253efc20 user: AAsk1902 | |
16:18 | • Reply: Feature Request: shell prompt for query parameters artifact: cff54a31d6 user: kmedcalf | |
16:04 | • Reply: Feature Request: shell prompt for query parameters artifact: 913295681c user: dkfellows | |
15:54 | • Reply: Request: stored functions/procedures artifact: 46ab9d771a user: wmacevoy | |
14:30 | • Reply: Reverse function seems to work, missing in documentation? artifact: 821c0893f4 user: kmedcalf | |
14:16 | • Reply: Reverse function seems to work, missing in documentation? artifact: 634ec6a7cc user: kmedcalf | |
14:09 | • Edit: Reverse function seems to work, missing in documentation? artifact: 98e38073b9 user: ralfbertling | |
14:08 | • Reply: CURRENT_TIMESTAMP is what? artifact: df52a24536 user: kmedcalf | |
14:07 | • Post: Reverse function seems to work, missing in documentation? artifact: 4f3a7f42f8 user: ralfbertling | |
14:01 | • Reply: Feature Request: shell prompt for query parameters artifact: c2a7eccabd user: kmedcalf | |
14:00 | • Reply: 2023 SQL standard foundation document published artifact: bcc84ef60f user: dkfellows | |
13:58 | • Post: Feature Request: shell prompt for query parameters artifact: 062482ffca user: dkfellows | |
13:55 | • Reply: How is a count(*) index decided? artifact: 0a73d1faae user: dan | |
13:48 | • Reply: How is a count(*) index decided? artifact: 118702f955 user: sqlitening | |
12:59 | • Reply: Report bugs against SQLite. artifact: bfbdc5b264 user: larrybr | |
12:54 | • Reply: 2023 SQL standard foundation document published artifact: 4ec4c54a9e user: holgerj | |
12:25 | • Post: Report bugs against SQLite. artifact: f8c14a1134 user: 740931 | |
11:46 | • Reply: SQLITE_BUSY & SQLITE_LOCKED artifact: 2473047b27 user: paulvh | |
11:18 | • Reply: Forcing read only access artifact: 30e17d9b42 user: AAsk1902 | |
08:57 | • Edit reply: SQLITE_BUSY & SQLITE_LOCKED artifact: dfdc13ec4f user: sqweek | |
08:56 | • Reply: SQLITE_BUSY & SQLITE_LOCKED artifact: bf283a5a0a user: sqweek | |
07:17 | • Reply: SQLITE_BUSY & SQLITE_LOCKED artifact: 7d52bf3f03 user: paulvh | |
3 Years Ago (more context)
2022-06-02
| ||
21:08 | • Reply: Unexpected Result by WHERE Again artifact: de16c4abe2 user: drh | |
18:41 | • Edit reply: Operator precedence bug artifact: bee24db5ed user: kmedcalf | |
18:39 | • Reply: Operator precedence bug artifact: 025c6c7f44 user: kmedcalf | |
18:08 | • Reply: Operator precedence bug artifact: c2ee57e7ee user: kmedcalf | |
17:12 | • Reply: Operator precedence bug artifact: 3ee826f6ea user: anonymous | |
15:23 | • Reply: Question about sqlite thread safe mode? artifact: c5062110ed user: larrybr | |
15:09 | • Reply: Redundant way to access shell in sqlite3.exe? artifact: 56723e91ff user: larrybr | |
15:06 | • Reply: Redundant way to access shell in sqlite3.exe? artifact: ad7c8ea125 user: stephan | |
14:53 | • Reply: Question about sqlite thread safe mode? artifact: 7b8d4cbbc1 user: gunter_hick | |
14:50 | • Reply: Operator precedence bug artifact: 23beeb96e6 user: larrybr | |
14:28 | • Post: Redundant way to access shell in sqlite3.exe? artifact: d4765bf482 user: oezmaster | |
14:02 | • Reply: Question about sqlite thread safe mode? artifact: a2c0df56f8 user: anonymous | |
14:02 | • Reply: Question about sqlite thread safe mode? artifact: 56462dfdf2 user: anonymous | |
13:46 | • Post: Unexpected Result by WHERE Again artifact: 15c93b54bf user: bajinsheng | |
12:54 | • Post: bug: sqlite3_changes returns incorrect value for UPDATE..RETURNING when table was dropped/created a second time on connection artifact: 33ea0f369f user: zzzeek | |
12:43 | • Reply: forum search limitations artifact: 73fc31b2b8 user: anonymous | |
12:33 | • Reply: Question about sqlite thread safe mode? artifact: 60d71b8dcd user: gunter_hick | |
12:03 | • Reply: Question about sqlite thread safe mode? artifact: f07708b197 user: drh | |
11:30 | • Reply: Question about sqlite thread safe mode? artifact: 7d94907e32 user: anonymous | |
10:06 | • Reply: Question about sqlite thread safe mode? artifact: c77a3de2a3 user: gunter_hick | |
09:53 | • Reply: Usage: .read FILE - Read file doseont work artifact: 97418377e3 user: Gael4429 | |
08:43 | • Post: Question about sqlite thread safe mode? artifact: 1726f1957e user: anonymous | |
08:29 | • Reply: View with CTE no longer works artifact: 94a8d22dca user: zimpenfish | |
07:50 | • Reply: Incorrect ".mode" display artifact: 94851bd53e user: stephan | |
07:37 | • Reply: Incorrect ".mode" display artifact: cbd5de9515 user: hanche | |
05:10 | • Reply: Operator precedence bug artifact: 7fb96306b7 user: rmariani | |
01:56 | • Post: System.Data.SQLite version 1.0.116.0 released artifact: e786475eab user: mistachkin | |
4 Years Ago (more context)
2021-06-02
| ||
19:02 | • Reply: memory vs mmap artifact: c814109b19 user: cladisch | |
14:53 | • Reply: Bug report: a bug in VIEW artifact: ed2bd4cab7 user: krking | |
14:38 | • Reply: Bug report: a bug in VIEW artifact: 4638b794d3 user: drh | |
14:20 | • Reply: Bug report: a bug in VIEW artifact: 79d53aa4ac user: dan | |
13:39 | • Reply: Complex view breaking SQLite on Android < v11 artifact: dc3f32e5b7 user: knu | |
13:31 | • Edit: Bug report: a bug in VIEW artifact: 02d7be94d7 user: krking | |
13:26 | • Edit reply: Bug report: a bug in VIEW artifact: b946a51948 user: krking | |
13:20 | • Edit reply: Bug report: a bug in VIEW artifact: 519d7d4812 user: krking | |
13:12 | • Reply: Bug report: a bug in VIEW artifact: b8d719119e user: krking | |
13:05 | • Post: DBSTAT docs example potentially misleading artifact: 53df207d16 user: dnamlin | |
12:47 | • Reply: Query performance regression after v3.33.0 (OP_SeekScan?) artifact: 01f5bc23da user: drh | |
12:28 | • Reply: Bug report: a bug in VIEW artifact: 90fba2127e user: drh | |
12:21 | • Reply: Complex view breaking SQLite on Android < v11 artifact: 752ceb4ac6 user: pierreknx | |
11:04 | • Edit reply: memory vs mmap artifact: c711d0a331 user: wyoung | |
10:29 | • Reply: How to convert the data type of the new column in the view? artifact: a437bbbf0e user: kmedcalf | |
09:32 | • Post: How to convert the data type of the new column in the view? artifact: 35d250d644 user: anonymous | |
09:31 | • Edit reply: memory vs mmap artifact: 1d811bd607 user: wyoung | |
09:28 | • Reply: memory vs mmap artifact: 0cb5701e14 user: wyoung | |
08:46 | • Post: Bug report: a bug in VIEW artifact: fcf2b46ab2 user: krking | |
08:09 | • Reply: memory vs mmap artifact: c2ffb39009 user: cladisch | |
02:25 | • Reply: Query performance regression after v3.33.0 (OP_SeekScan?) artifact: 9c3e117cb2 user: dnamlin | |
02:14 | • Reply: What am I doing wrong to get errors when trying to compile amalgamation file in Linux artifact: 9718b4f7ac user: 1codedebugger | |
00:49 | • Reply: Query performance regression after v3.33.0 (OP_SeekScan?) artifact: 2ad5681eb0 user: kmedcalf | |
5 Years Ago (more context)
2020-06-02
| ||
23:54 | • Reply: Feature Request: pragma to curb bad column expectations artifact: 00075f7eb9 user: kmedcalf | |
23:47 | • Reply: SQLIGHT performance artifact: 83cc8b081f user: anonymous | |
23:09 | • Post: Standard Deiation/Variance Aggregate Functions artifact: 037d48c82e user: rgarnett1955 | |
21:51 | • Reply: SELECT * Column Sequence / Order (not ORDER BY) artifact: bd409912dc user: rhb327 | |
21:50 | • Reply: SELECT * Column Sequence / Order (not ORDER BY) artifact: 0ff367c07e user: rhb327 | |
21:48 | • Edit: Password-protected databases no longer work with 1.113, no rollback possible artifact: e5a5545a9a user: pbickford | |
21:46 | • Reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: 4851b51ca7 user: pbickford | |
21:19 | • Post: Feature Request: pragma to curb bad column expectations artifact: 3b4a4ce920 user: cuz | |
20:58 | • Edit reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: 7d52eea167 user: utelle | |
20:56 | • Reply: SELECT * Column Sequence / Order (not ORDER BY) artifact: 404317e3db user: cuz | |
20:49 | • Reply: Password-protected databases no longer work with 1.113, no rollback possible artifact: 1626e90f98 user: utelle | |
20:46 | • Reply: SQLIGHT performance artifact: ee2aae963c user: drh | |
20:38 | • Reply: SQLIGHT performance artifact: 550ab24269 user: drh | |
20:34 | • Reply: SELECT * Column Sequence / Order (not ORDER BY) artifact: c187f45b09 user: drh | |
20:03 | • Post: SELECT * Column Sequence / Order (not ORDER BY) artifact: 56d731d2fc user: rhb327 | |
19:34 | • Post: Password-protected databases no longer work with 1.113, no rollback possible artifact: 6d735975b7 user: pbickford | |
16:50 | • Reply: Unexepected commit result with two threads application artifact: 29a05d0d62 user: Maxulite | |
16:44 | • Reply: SQLIGHT performance artifact: 271a81ab57 user: cuz | |
16:08 | • Reply: SQLIGHT performance artifact: 210bba00a0 user: akreidly | |
16:03 | • Post: Closing app hang with loaded SQLite 3.32.01 artifact: 387a97ec84 user: codeservice | |
15:30 | • Reply: Unexepected commit result with two threads application artifact: 0e88c45f45 user: Maxulite | |
15:20 | • Reply: SQLIGHT performance artifact: dc31d6c286 user: LarryBrasfield | |
15:18 | • Edit reply: Unexepected commit result with two threads application artifact: eea22efe94 user: slavin | |
15:17 | • Reply: Unexepected commit result with two threads application artifact: bc30e16812 user: slavin | |
14:53 | • Edit reply: Unexepected commit result with two threads application artifact: 6733e55523 user: LarryBrasfield | |
14:53 | • Reply: Unexepected commit result with two threads application artifact: e3bee93b23 user: LarryBrasfield | |
14:42 | • Reply: No threads older than ~ 82 days? artifact: df9c29cbcb user: drh | |
14:15 | • Post: No threads older than ~ 82 days? artifact: 3add492b6c user: anonymous | |
13:36 | • Reply: Unexepected commit result with two threads application artifact: 9d833bf6c0 user: Maxulite | |
12:45 | • Post: SQLIGHT performance artifact: 4c7562f11c user: akreidly | |
12:22 | • Reply: Why is this query giving results below 100 artifact: 9916c0d8f1 user: drh | |
12:05 | • Reply: Why is this query giving results below 100 artifact: f3eda3cfc5 user: stephan | |
12:01 | • Post: Why is this query giving results below 100 artifact: d320b37122 user: BlakeCAtlanta | |
11:14 | • Reply: Unexepected commit result with two threads application artifact: 9eca70676c user: Maxulite | |
10:36 | • Reply: Unexepected commit result with two threads application artifact: f92837e383 user: sqweek | |
09:59 | • Post: Unexepected commit result with two threads application artifact: ba6f754fc2 user: Maxulite | |
09:07 | • Reply: Cache rebuild fails artifact: 9dfbcd7327 user: stephan | |
03:24 | • Reply: Question about aliases on SELECT artifact: 26a82df9bc user: kmedcalf | |
02:51 | • Reply: Cache rebuild fails artifact: d9c53deced user: fantajista | |
02:15 | • Reply: SQLite turns 20 artifact: a295e4cc9f user: tb13 | |
01:44 | • Reply: Cache rebuild fails artifact: 310b8eda4f user: fantajista | |
00:32 | • Post: Question about aliases on SELECT artifact: 906ca360d6 user: doug9forester | |