This Day In History For 2025-06-27
1 Year Ago (more context)
|
2024-06-27
| ||
| 23:57 | • Reply: How to perform Regex Update query? artifact: 89579360bc user: alexgarciaxyz | |
| 23:30 | • Post: Possible virtual table bug: result_subtype is passed to INSERT values but not UPDATE values artifact: 65317ce9c6 user: alexgarciaxyz | |
| 23:06 | • Post: FTS5: xPhraseFirst/Next order artifact: f4e6bb64ee user: rogerbinns | |
| 22:14 | • Post: How to perform Regex Update query? artifact: 7c7360b99c user: paul1149 | |
| 21:51 | • Reply: Calculating using times (HH:MM) format artifact: b2baf804b4 user: anonymous | |
| 15:56 | • Edit reply: Calculating using times (HH:MM) format artifact: d592e3acac user: holgerj | |
| 15:56 | • Reply: Calculating using times (HH:MM) format artifact: d2cdade27d user: holgerj | |
| 15:15 | • Post: Datetime function format modifier (a proposal) artifact: 404396d40e user: dmausner | |
| 15:06 | • Reply: Calculating using times (HH:MM) format artifact: 3ae77e98ac user: stephan | |
| 14:56 | • Reply: Calculating using times (HH:MM) format artifact: 02b2c82e72 user: punkish | |
| 14:42 | • Reply: simple request, many db and variables, speed question artifact: a0e1c5da26 user: mark | |
| 14:36 | • Reply: simple request, many db and variables, speed question artifact: 876945e75d user: mark | |
| 13:34 | • Reply: Calculating using times (HH:MM) format artifact: c176254c08 user: anonymous | |
| 11:33 | • Edit reply: Calculating using times (HH:MM) format artifact: b98d8d9bd8 user: spindrift | |
| 11:29 | • Reply: simple request, many db and variables, speed question artifact: 19cc0909f3 user: spindrift | |
| 11:07 | • Reply: simple request, many db and variables, speed question artifact: da6a9d4f6a user: Pogzy321 | |
| 10:30 | • Reply: simple request, many db and variables, speed question artifact: ce47458432 user: spindrift | |
| 10:29 | • Reply: Calculating using times (HH:MM) format artifact: 7377e201e9 user: andydoc1 | |
| 10:17 | • Reply: simple request, many db and variables, speed question artifact: e9aae947ac user: gunter_hick | |
| 09:52 | • Reply: Ask for the "PrivacyInfo.xcprivacy" required by Apple artifact: 6555ac13b8 user: baihao_buaa | |
| 09:50 | • Post: simple request, many db and variables, speed question artifact: 04e6095f4d user: Pogzy321 | |
| 08:40 | • Reply: Calculating using times (HH:MM) format artifact: 73a0ff3213 user: spindrift | |
| 07:11 | • Reply: Calculating using times (HH:MM) format artifact: 4419848924 user: larrybr | |
| 06:47 | • Reply: Calculating using times (HH:MM) format artifact: 1f75dce053 user: anonymous | |
| 06:46 | • Reply: Calculating using times (HH:MM) format artifact: 803c9b8f8c user: spindrift | |
| 06:43 | • Reply: Calculating using times (HH:MM) format artifact: 60321cdd52 user: spindrift | |
| 06:08 | • Reply: Calculating using times (HH:MM) format artifact: bc4b0b8a56 user: andydoc1 | |
| 05:56 | • Reply: Calculating using times (HH:MM) format artifact: 09a41a05d3 user: gunter_hick | |
| 05:42 | • Reply: Calculating using times (HH:MM) format artifact: c11311e695 user: andydoc1 | |
| 05:01 | • Reply: Calculating using times (HH:MM) format artifact: 088b2d09ce user: anonymous | |
| 04:50 | • Reply: Calculating using times (HH:MM) format artifact: e0b234398f user: larrybr | |
2 Years Ago (more context)
|
2023-06-27
| ||
| 20:50 | • Reply: Confused about concurrency and sychronization artifact: 11f9e983b3 user: Helios | |
| 20:46 | • Reply: Confused about concurrency and sychronization artifact: c324e6c21f user: Helios | |
| 20:34 | • Edit reply: Resolve hyperlink path from field name artifact: 219c26611b user: kmedcalf | |
| 20:31 | • Edit reply: Resolve hyperlink path from field name artifact: 5610828f6a user: kmedcalf | |
| 20:30 | • Reply: Resolve hyperlink path from field name artifact: 29c2cd9f8b user: kmedcalf | |
| 20:25 | • Reply: Resolve hyperlink path from field name artifact: 1ec947cbe6 user: kmedcalf | |
| 20:21 | • Edit reply: Resolve hyperlink path from field name artifact: b69a7e4987 user: kmedcalf | |
| 20:21 | • Reply: Resolve hyperlink path from field name artifact: 1662a10740 user: kmedcalf | |
| 20:14 | • Reply: Confused about concurrency and sychronization artifact: abf3798bd7 user: kmedcalf | |
| 20:12 | • Reply: Confused about concurrency and sychronization artifact: f8a6866ebd user: kmedcalf | |
| 19:45 | • Reply: Resolve hyperlink path from field name artifact: f1fd22ee68 user: Poco90 | |
| 18:41 | • Reply: Confused about concurrency and sychronization artifact: 60f7501cb9 user: Helios | |
| 18:26 | • Reply: Confused about concurrency and sychronization artifact: 4040daabcb user: kmedcalf | |
| 18:24 | • Reply: Confused about concurrency and sychronization artifact: 175b10eadd user: kmedcalf | |
| 17:26 | • Reply: Confused about concurrency and sychronization artifact: fe132a7a7a user: kmedcalf | |
| 17:20 | • Reply: Confused about concurrency and sychronization artifact: f9a190d9f9 user: kmedcalf | |
| 16:29 | • Reply: Confused about concurrency and sychronization artifact: 9d82cf0215 user: Helios | |
| 15:53 | • Edit: sqlite3GlobalConfig.m.xMalloc gets back to null after initializing it to the default artifact: 7a2c1b6a0c user: marcob | |
| 15:29 | • Reply: Confused about concurrency and sychronization artifact: b0341efb0f user: gunter_hick | |
| 15:13 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: 1a587e3e55 user: gunter_hick | |
| 14:54 | • Reply: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: c6bf5a859f user: anshumap | |
| 14:48 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: f0d671e343 user: scasaletto | |
| 14:29 | • Reply: xBestIndex called with nConstraint=0 when using LIKE exp ESCAPE '_' artifact: 89a317c727 user: scasaletto | |
| 14:20 | • Post: sqlite3GlobalConfig.m.xMalloc gets back to null after initializing it to the default artifact: 21da853c1e user: marcob | |
| 13:52 | • Reply: Confused about concurrency and sychronization artifact: 22818b4a52 user: Helios | |
| 13:31 | • Reply: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: a0d5565bc0 user: drh | |
| 13:19 | • Reply: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: 7bb7ef0161 user: jicman | |
| 13:15 | • Edit: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: c705d8fe77 user: anshumap | |
| 11:11 | • Reply: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: fa5637f6a8 user: anonymous | |
| 11:00 | • Post: Observed drastic performance degradation in UPDATE..FROM...WHERE query after moving from 3.36.0 to 3.42.0 artifact: 1aa9b0a520 user: anshumap | |
| 08:47 | • Reply: .sha3sum failed on tables with specific contents artifact: 8052a5bfee user: sorcix | |
| 06:56 | • Reply: Confused about concurrency and sychronization artifact: c465b3f9f3 user: gunter_hick | |
| 06:21 | • Reply: Confused about concurrency and sychronization artifact: 3fcb28104c user: Helios | |
| 05:34 | • Reply: Confused about concurrency and sychronization artifact: fdea00efe5 user: gunter_hick | |
| 03:25 | • Post: Confused about concurrency and sychronization artifact: 735371d954 user: Helios | |
| 00:14 | • Reply: Reading SQL from Windows Clipboard artifact: 109572547e user: larrybr | |
3 Years Ago (more context)
|
2022-06-27
| ||
| 22:08 | • Reply: Unclear why join is so much slower than separate queries artifact: af57b56a0f user: jimmorris33215 | |
| 22:05 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: ed6ba7ce56 user: kmedcalf | |
| 21:56 | • Reply: Status of wal2 branch artifact: 52ed11b87e user: pgregory | |
| 21:54 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 37741fdece user: kmedcalf | |
| 21:52 | • Reply: question about json_quote artifact: e9b46a818f user: younique | |
| 21:47 | • Reply: Status of wal2 branch artifact: 2c30cddf94 user: dan | |
| 21:42 | • Reply: R-TREE SQLITE minx, maxx,miny,maxy accuracy artifact: 6cc7262cad user: greglearns | |
| 20:58 | • Reply: Unclear why join is so much slower than separate queries artifact: b5166e2d57 user: anonymous | |
| 20:30 | • Post: Unclear why join is so much slower than separate queries artifact: ad5efebc88 user: christoph | |
| 20:24 | • Reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: b0da75a947 user: anonymous | |
| 20:23 | • Reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: 4507b8ad1d user: anonymous | |
| 20:22 | • Reply: question about wal EXCLUSIVE mode artifact: 4ad4f3cb3c user: anonymous | |
| 20:22 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: dd09427fb3 user: anonymous | |
| 19:42 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 78005e3435 user: 164896512 | |
| 19:41 | • Reply: parallel buils broken artifact: dd8b9be2d1 user: andyrtr | |
| 19:32 | • Post: Request for ENH. XML in the CLI - but only a bit. artifact: 8fd9d9b7d3 user: midijohnny | |
| 19:15 | • Post: question about wal EXCLUSIVE mode artifact: d2adbd9d8b user: anonymous | |
| 19:07 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 04457fd0e9 user: 164896512 | |
| 19:05 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 8fc0e0aed1 user: 164896512 | |
| 18:28 | • Reply: Numerical stability of AVG and SUM artifact: a0b458d8ef user: kmedcalf | |
| 18:03 | • Reply: Database does not update artifact: a3add27308 user: hanche | |
| 16:49 | • Reply: Status of wal2 branch artifact: 228884971d user: pgregory | |
| 16:24 | • Reply: combining 2 tables artifact: 607efdcd4d user: larrybr | |
| 15:50 | • Reply: Status of wal2 branch artifact: 270ab832f9 user: pgregory | |
| 15:40 | • Post: combining 2 tables artifact: 2ca29f58c2 user: anonymous | |
| 15:36 | • Reply: WHERE NOT IN query plan optimization artifact: cd12a52b30 user: ddevienne | |
| 15:16 | • Edit reply: Database does not update artifact: d23455c362 user: chrisjlocke1 | |
| 15:14 | • Reply: Database does not update artifact: c9e510bd01 user: chrisjlocke1 | |
| 15:11 | • Reply: WHERE NOT IN query plan optimization artifact: 27c605852c user: dan | |
| 14:31 | • Post: Database does not update artifact: 56d6e66ad8 user: gagsters888 | |
| 13:56 | • Reply: Status of wal2 branch artifact: 49cef62bba user: dan | |
| 12:56 | • Reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: 5bb7988ca4 user: kjames3411 | |
| 12:29 | • Edit reply: Status of wal2 branch artifact: 3c67f1b456 user: pgregory | |
| 12:25 | • Reply: parallel buils broken artifact: 98df1a61b9 user: drh | |
| 12:18 | • Reply: Numerical stability of AVG and SUM artifact: d9b60ada09 user: dkfellows | |
| 12:03 | • Edit reply: Status of wal2 branch artifact: 47676c1a26 user: pgregory | |
| 11:58 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 865b4d5184 user: billwade | |
| 11:35 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: a1365bdf7b user: gunter_hick | |
| 10:58 | • Reply: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: d954124f6b user: dkfellows | |
| 10:45 | • Edit reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: 819c49b937 user: dkfellows | |
| 10:45 | • Reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: a5c2116028 user: dkfellows | |
| 09:57 | • Reply: Status of wal2 branch artifact: 34086bd44a user: pgregory | |
| 09:54 | • Post: WHERE NOT IN query plan optimization artifact: b8aab3d863 user: ddevienne | |
| 09:32 | • Edit: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: 252355ed7d user: 164896512 | |
| 08:58 | • Post: Why UPDATEs are faster when WHERE key is sorted? How to improve performance? artifact: c106c6ccd2 user: 164896512 | |
| 07:12 | • Reply: R-TREE SQLITE minx, maxx,miny,maxy accuracy artifact: 18628420b5 user: ddevienne | |
| 00:50 | • Reply: Two flaws in the design of SQLite, which should be easily to be fixed artifact: 7434e0100d user: anonymous | |
4 Years Ago (more context)
|
2021-06-27
| ||
| 22:53 | • Reply: cannot create tables in sqlitestudio than other apps can see artifact: 85168394d3 user: larrybr | |
| 21:23 | • Post: cannot create tables in sqlitestudio than other apps can see artifact: f2a2c97b24 user: steveinalabama | |
| 21:19 | • Reply: New version of app, more columns for same table artifact: acada806ff user: anonymous | |
| 20:08 | • Reply: System.DllNotFoundException on MonoDevelop artifact: a1bda0ade0 user: larrybr | |
| 20:03 | • Reply: New version of app, more columns for same table artifact: b1b6f06e58 user: RichardDamon | |
| 19:51 | • Reply: New version of app, more columns for same table artifact: 0f22c02435 user: anonymous | |
| 19:44 | • Reply: New version of app, more columns for same table artifact: 012a204ebd user: larrybr | |
| 19:29 | • Reply: Will SQLite support GQL or SQL/PGQ in the future? artifact: 4b03ff6718 user: slavin | |
| 19:28 | • Delete reply: Will SQLite support GQL or SQL/PGQ in the future? artifact: f2eaf07826 user: slavin | |
| 19:00 | • Reply: New version of app, more columns for same table artifact: dfc8d8b622 user: anonymous | |
| 17:39 | • Reply: New version of app, more columns for same table artifact: c78566ac57 user: larrybr | |
| 17:22 | • Post: New version of app, more columns for same table artifact: 492188cb23 user: anonymous | |
| 17:18 | • Post: System.DllNotFoundException on MonoDevelop artifact: 544f1b04b0 user: BanditoWalrus | |
| 15:30 | • Reply: Changing the checksum VFS artifact: 4f116e6af2 user: slavin | |
| 15:19 | • Reply: Will SQLite support GQL or SQL/PGQ in the future? artifact: b71b17cd12 user: slavin | |
| 15:04 | • Edit reply: Merge Data artifact: 2a25aee8ae user: larrybr | |
| 14:37 | • Reply: Merge Data artifact: ec7470c76f user: larrybr | |
| 11:05 | • Reply: Will SQLite support GQL or SQL/PGQ in the future? artifact: e463f2536f user: RoboManni | |
| 10:31 | • Reply: Feature request: Stored Procedures artifact: 7f55482020 user: RoboManni | |
| 02:17 | • Reply: Better download file naming artifact: 475d3c6dc5 user: doug9forester | |
5 Years Ago (more context)
|
2020-06-27
| ||
| 21:17 | • Reply: SQLITE_HAS_CODE is gone? artifact: 1b9e6264ed user: alaskanarcher | |
| 15:35 | • Edit reply: Problem with Sqlite DELETE documentation artifact: 0630cd5987 user: luuk | |
| 15:34 | • Reply: Problem with Sqlite DELETE documentation artifact: d436f8ab6e user: luuk | |
| 14:51 | • Reply: Query planner fails to use obvious index artifact: ff3a80de99 user: kmedcalf | |
| 13:56 | • Reply: Query planner fails to use obvious index artifact: ab94f3ad9f user: knu | |
| 12:20 | • Reply: Problem with Sqlite DELETE documentation artifact: a7edb11d72 user: LarryBrasfield | |
| 12:06 | • Reply: Problem with Sqlite DELETE documentation artifact: c2ca25c1ad user: kmedcalf | |
| 11:49 | • Reply: Problem with Sqlite DELETE documentation artifact: b6ae700a40 user: slavin | |
| 10:12 | • Reply: Query planner fails to use obvious index artifact: 1fe7488810 user: luuk | |