This Day In History For 2025-10-18
1 Year Ago (more context)
|
2024-10-18
| ||
| 22:37 | • Post: More sqlite3_rsync issues artifact: e055d50821 user: _blgl_ | |
| 18:37 | • Post: Relation: token, token pairs and try select artifact: f70ab4f062 user: Andrzej | |
| 15:47 | • Reply: sqlite wasm custom builds artifact: 2ca9e0a416 user: lexfiend | |
| 14:43 | • Reply: sqlite wasm custom builds artifact: 40543f40da user: wyoung | |
| 12:25 | • Reply: sqlite wasm custom builds artifact: 0a9aaa9180 user: stephan | |
| 07:38 | • Reply: When and why we get SQLITE_BUSY when it's unable to open the database file. artifact: 198a529ab5 user: sunpeng | |
| 06:25 | • Edit reply: Is `pragma mmap_size` still considered dangerous on macOS? artifact: 9520418395 user: numist | |
| 06:14 | • Edit reply: Is `pragma mmap_size` still considered dangerous on macOS? artifact: 84ca672b40 user: numist | |
| 06:10 | • Reply: When and why we get SQLITE_BUSY when it's unable to open the database file. artifact: 8b6dc0b156 user: yangbingjie | |
| 06:08 | • Reply: When and why we get SQLITE_BUSY when it's unable to open the database file. artifact: be7969c84e user: yangbingjie | |
| 05:02 | • Reply: Is `pragma mmap_size` still considered dangerous on macOS? artifact: ee84954056 user: numist | |
| 04:18 | • Reply: Is `pragma mmap_size` still considered dangerous on macOS? artifact: d3c42cefa5 user: numist | |
| 03:59 | • Reply: When and why we get SQLITE_BUSY when it's unable to open the database file. artifact: 684fbafc3d user: simonw | |
| 03:33 | • Reply: Possible regression for read-only databases in 3.46.1 (WASM) artifact: bbbd1c6fd4 user: DallasHoff | |
| 02:55 | • Post: Different query plans when joining via ON vs. USING artifact: 06b8a9cf39 user: anonymous | |
| 01:46 | • Post: When and why we get SQLITE_BUSY when it's unable to open the database file. artifact: 9a2068500d user: yangbingjie | |
| 01:44 | • Reply: sqlite wasm custom builds artifact: e57932e3cc user: FakeUser | |
| 00:44 | • Reply: Better docs for BEGIN IMMEDIATE TRANSACTION and SQLITE_BUSY artifact: 2b1c13c851 user: simonw | |
| 00:43 | • Post: Better docs for BEGIN IMMEDIATE TRANSACTION and SQLITE_BUSY artifact: 5ed1b0217e user: simonw | |
| 00:42 | • Reply: sqlite wasm custom builds artifact: 14e75f7455 user: stephan | |
| 00:27 | • Reply: sqlite wasm custom builds artifact: e046ee7658 user: FakeUser | |
2 Years Ago (more context)
|
2023-10-18
| ||
| 23:53 | • Edit reply: sqlite3-CLI unintended? behaviour artifact: 1cd8fa8133 user: larrybr | |
| 23:48 | • Reply: sqlite3-CLI unintended? behaviour artifact: b76325eb30 user: larrybr | |
| 22:17 | • Reply: sqlite3-CLI unintended? behaviour artifact: 3debcf2ebd user: anonymous | |
| 21:09 | • Reply: sqlite3-CLI unintended? behaviour artifact: d3ced7f5fe user: larrybr | |
| 20:45 | • Post: sqlite3-CLI unintended? behaviour artifact: 3cc561eb7f user: anonymous | |
| 17:33 | • Reply: SQLite with SEE on .NET, Android and IOS artifact: b882ba97c7 user: jicman | |
| 17:26 | • Reply: SQLite with SEE on .NET, Android and IOS artifact: 5f7d9ef22c user: Ted145 | |
| 17:15 | • Post: Checkin [bfd8d910] fails on i686 artifact: ffcbf789b5 user: reimax | |
| 15:20 | • Reply: Getting Column does not belong to table exception artifact: 57e134175b user: larrybr | |
| 14:47 | • Post: Getting Column does not belong to table exception artifact: 99d640459f user: sanketj | |
| 13:35 | • Reply: SQLite .NET: CommandBuilder performs really bad on tables with a lot of indexes artifact: fcfe84fd20 user: Ted145 | |
| 13:28 | • Reply: Can the views pro week be done with a weeknumber artifact: f94d150e05 user: cuz | |
| 13:12 | • Reply: Can the views pro week be done with a weeknumber artifact: 7c13f81e58 user: gunter_hick | |
| 13:05 | • Post: Can the views pro week be done with a weeknumber artifact: 6803b92b92 user: CecilWesterhof | |
| 11:36 | • Reply: Potential query planner optimization for queries containing "NOT IN (<subquery>)" artifact: 4aa22b8e52 user: gunter_hick | |
| 10:59 | • Reply: CREATE TABLE's table-constraint syntax does not allow AUTOINCREMENT, but it works. artifact: be50fae9a1 user: gunter_hick | |
| 09:03 | • Post: CREATE TABLE's table-constraint syntax does not allow AUTOINCREMENT, but it works. artifact: 77468323b2 user: twisterrob | |
| 08:16 | • Reply: (Deleted) artifact: 8807187722 user: mark | |
| 07:26 | • Edit reply: UNIQUE column allowing only a single NULL value artifact: 55a43fa2a6 user: mark | |
| 07:17 | • Reply: UNIQUE column allowing only a single NULL value artifact: 50c4af7b8c user: mark | |
| 03:57 | • Reply: DSQLITE_THREADSAFE option not working expected when imported in the test project artifact: ac669fd370 user: larrybr | |
| 01:57 | • Post: DSQLITE_THREADSAFE option not working expected when imported in the test project artifact: abfc80c8b4 user: Staples | |
3 Years Ago (more context)
|
2022-10-18
| ||
| 23:52 | • Reply: Some peeks in execution time artifact: d3c0c86751 user: anonymous | |
| 20:31 | • Reply: Some peeks in execution time artifact: 3332e730d5 user: Maryam | |
| 20:28 | • Reply: Some peeks in execution time artifact: 82c193056d user: Maryam | |
| 20:21 | • Reply: Some peeks in execution time artifact: c3ebd1484f user: Maryam | |
| 20:11 | • Reply: store dimensions that never change in normalized form or columns? artifact: faaf70a1d9 user: anonymous | |
| 20:01 | • Reply: Should `index_info` return `null` for rowid columns? artifact: c1147532c1 user: anonymous | |
| 19:43 | • Reply: Should `index_info` return `null` for rowid columns? artifact: e798f5cae2 user: kmedcalf | |
| 19:11 | • Reply: store dimensions that never change in normalized form or columns? artifact: 7d24ae4da6 user: slavin | |
| 18:25 | • Reply: Should `index_info` return `null` for rowid columns? artifact: 5f9e9bb7d7 user: anonymous | |
| 18:20 | • Reply: VACUUM INTO 'other.db' and fsync artifact: 4be1d7a63d user: anonymous | |
| 18:14 | • Edit reply: Should `index_info` return `null` for rowid columns? artifact: b96b21dd62 user: kmedcalf | |
| 18:14 | • Reply: Should `index_info` return `null` for rowid columns? artifact: 982a320931 user: kmedcalf | |
| 18:01 | • Edit reply: Should `index_info` return `null` for rowid columns? artifact: 11617ad2fa user: kmedcalf | |
| 18:00 | • Reply: Should `index_info` return `null` for rowid columns? artifact: b44e2eafa4 user: kmedcalf | |
| 17:32 | • Reply: Should `index_info` return `null` for rowid columns? artifact: 46d8869cf4 user: anonymous | |
| 17:02 | • Reply: Should `index_info` return `null` for rowid columns? artifact: a123a8b809 user: dvdraymond | |
| 16:51 | • Post: store dimensions that never change in normalized form or columns? artifact: 88b4b443db user: biodrool | |
| 16:28 | • Reply: Should `index_info` return `null` for rowid columns? artifact: d5a390999d user: anonymous | |
| 15:53 | • Reply: Should `index_info` return `null` for rowid columns? artifact: e0605a7a3f user: kmedcalf | |
| 15:22 | • Post: Should `index_info` return `null` for rowid columns? artifact: 44247968e3 user: anonymous | |
| 13:44 | • Reply: Contentless trigram indexes and GLOB/LIKE in FTS artifact: 985badf249 user: dan | |
| 13:36 | • Reply: Contentless trigram indexes and GLOB/LIKE in FTS artifact: 94404e9979 user: jicman | |
| 11:28 | • Post: Contentless trigram indexes and GLOB/LIKE in FTS artifact: 13f022dc7b user: crtxcr | |
| 09:50 | • Reply: Clarification on VACUUMing artifact: 509cf29e84 user: ddevienne | |
| 09:39 | • Reply: Clarification on VACUUMing artifact: 1dc014f07c user: slavin | |
| 08:52 | • Reply: soliciting ideas on how to store and query XMLs artifact: fc754861e0 user: ddevienne | |
| 08:21 | • Post: Looking for nuget packages for SQLite version 113 artifact: 90af7d0b84 user: AlexNek | |
| 07:56 | • Post: VACUUM INTO 'other.db' and fsync artifact: 8c83764a73 user: willemv | |
| 06:05 | • Reply: Clarification on VACUUMing artifact: 1bcc956038 user: DiamondJohn | |
| 05:54 | • Reply: sqlite3_update_hook - which changes are consiered? artifact: cb4f351d86 user: gunter_hick | |
| 04:43 | • Reply: soliciting ideas on how to store and query XMLs artifact: 17345732dc user: anonymous | |
| 01:53 | • Reply: soliciting ideas on how to store and query XMLs artifact: a3fc6ff026 user: kbilleter | |
| 00:17 | • Reply: Case insensitivity not applied while coalescing artifact: 9fde33bcc8 user: kmedcalf | |
4 Years Ago (more context)
|
2021-10-18
| ||
| 18:32 | • Reply: SQLite Page Cache Subsystem as Library artifact: da4de69f2e user: gavinhoward | |
| 18:23 | • Reply: SQLite Page Cache Subsystem as Library artifact: dd608140b2 user: larrybr | |
| 18:04 | • Post: SQLite Page Cache Subsystem as Library artifact: 206b6db7ce user: gavinhoward | |
| 15:38 | • Reply: sqlite3_busy_handler missing artifact: e5242272b8 user: anonymous | |
| 12:00 | • Reply: x86_64/amd64 sqlite3 binaries artifact: 1dba1c6bc4 user: anonymous | |
| 08:06 | • Reply: Column names and aliases in expressions artifact: 2b07d62528 user: KevinYouren | |
| 07:25 | • Reply: Column names and aliases in expressions artifact: 4f1f5ff3f9 user: stephan | |
| 02:07 | • Edit reply: Column names and aliases in expressions artifact: 39c8dd277f user: stephan | |
| 01:32 | • Reply: Column names and aliases in expressions artifact: 5ed7b20e02 user: kmedcalf | |
| 01:01 | • Reply: Column names and aliases in expressions artifact: cf3e43fb16 user: casaderobison | |
| 00:14 | • Edit reply: Column names and aliases in expressions artifact: 6b0a817262 user: kmedcalf | |
| 00:12 | • Reply: Column names and aliases in expressions artifact: 9cb5b81d6b user: kmedcalf | |
| 00:02 | • Reply: Column names and aliases in expressions artifact: 43b8740461 user: kmedcalf | |