This Day In History For 2025-06-15
1 Year Ago (more context)
|
2024-06-15
| ||
| 23:08 | • Reply: informations on LSM extension of sqlite artifact: 599e155c01 user: anonymous | |
| 18:49 | • Reply: informations on LSM extension of sqlite artifact: 927ba292f6 user: darkmatter | |
| 15:11 | • Reply: informations on LSM extension of sqlite artifact: bd73907679 user: stephan | |
| 15:03 | • Reply: informations on LSM extension of sqlite artifact: 287a8515b9 user: anonymous | |
| 14:58 | • Reply: informations on LSM extension of sqlite artifact: 4f30afcbbc user: stephan | |
| 14:44 | • Post: informations on LSM extension of sqlite artifact: a342d8a0aa user: darkmatter | |
2 Years Ago (more context)
|
2023-06-15
| ||
| 21:06 | • Reply: System.Data.SQLite version 1.0.118.0 released artifact: 1768114570 user: mistachkin | |
| 20:35 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: a5b6a1a4db user: kmedcalf | |
| 20:31 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: bc0cd17bdd user: kmedcalf | |
| 14:11 | • Reply: like and virtual tables on database ascii 256 format artifact: 1762b12203 user: gunter_hick | |
| 13:17 | • Post: like and virtual tables on database ascii 256 format artifact: 999221e262 user: AAzanov | |
| 12:22 | • Reply: json_extract() doesn't work on json_valid artifact: 472df8e2d3 user: dbabits | |
| 10:23 | • Edit reply: dropping indexes before inserting… good, bad, maybe? artifact: 69bb00ef3c user: punkish | |
| 10:22 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 1d5417be30 user: punkish | |
| 10:01 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: b078698bc1 user: curmudgeon | |
| 09:25 | • Reply: "PRAGMA journal_mode" without effect ? artifact: ba1c1c3678 user: anonymous | |
| 06:56 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 8f8175054d user: spindrift | |
| 06:23 | • Reply: dropping indexes before inserting… good, bad, maybe? artifact: 189be79fc6 user: curmudgeon | |
3 Years Ago (more context)
|
2022-06-15
| ||
| 23:32 | • Reply: Multiple compression methods artifact: c876db7917 user: stephan | |
| 23:02 | • Post: Multiple compression methods artifact: e7c6310f40 user: Yairlenga | |
| 20:05 | • Edit reply: The changes() SQL function cannot be used as value for Returning? artifact: 0a12f24ae3 user: kmedcalf | |
| 19:58 | • Reply: The changes() SQL function cannot be used as value for Returning? artifact: 1a2501c6ef user: kmedcalf | |
| 19:38 | • Reply: Encrypt and decrypt SQLite database artifact: 509f10e3b0 user: SarahLeroy | |
| 18:30 | • Reply: The changes() SQL function cannot be used as value for Returning? artifact: 3fbc32dd98 user: anonymous | |
| 17:40 | • Reply: The changes() SQL function cannot be used as value for Returning? artifact: e2f35c18a6 user: anonymous | |
| 16:10 | • Edit reply: Unexpected Result by Complicated JOINING Again artifact: 9048d71f68 user: jicman | |
| 16:09 | • Reply: Unexpected Result by Complicated JOINING Again artifact: c3e417c0ec user: jicman | |
| 15:36 | • Reply: /docsrc: build docs are missing a step artifact: dc1415ee2b user: larrybr | |
| 09:46 | • Post: /docsrc: build docs are missing a step artifact: 44e979d1f6 user: stephan | |
| 00:06 | • Reply: Documentation "typo" artifact: 4967c2810d user: larrybr | |
4 Years Ago (more context)
|
2021-06-15
| ||
| 22:11 | • Reply: How to optimize writing from several processes? artifact: 01749076d7 user: lazyhiker | |
| 21:55 | • Reply: Extract files from sqlar with a directory prepended artifact: ace24d41dc user: 6kEs4Majrd | |
| 18:44 | • Reply: How to optimize writing from several processes? artifact: fe05c77ea7 user: drh | |
| 18:31 | • Post: How to optimize writing from several processes? artifact: c14366ed5c user: lazyhiker | |
| 16:58 | • Reply: Opening a DB with SQLITE_OPEN_EXCLUSIVE artifact: fd7f4730be user: kmedcalf | |
| 16:19 | • Reply: Opening a DB with SQLITE_OPEN_EXCLUSIVE artifact: b861a9afc5 user: billwade | |
| 15:17 | • Reply: Bug A NULL pointer dereference bug was discovered in SQLite artifact: cd6e9c0b61 user: drh | |
| 15:07 | • Reply: Opening a DB with SQLITE_OPEN_EXCLUSIVE artifact: d8a585ed17 user: wyoung | |
| 13:45 | • Reply: Opening a DB with SQLITE_OPEN_EXCLUSIVE artifact: f628d35f22 user: kmedcalf | |
| 13:36 | • Reply: A format string vulnerability in tool used to help build SQLite's TCL extension on Windows artifact: e83186e9ce user: larrybr | |
| 12:13 | • Reply: Opening a DB with SQLITE_OPEN_EXCLUSIVE artifact: bc77278d58 user: Benjamin | |
| 11:43 | • Reply: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: 47c7eb6802 user: drh | |
| 11:38 | • Edit: bug A stack buffer overflow vulnerability was discovered in SQLite 3.36.0 artifact: d036c2b547 user: salmonx | |
| 11:34 | • Reply: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: 64e9895d18 user: salmonx | |
| 11:30 | • Edit: A format string vulnerability in tool used to help build SQLite's TCL extension on Windows artifact: 7f0beca979 user: salmonx | |
| 11:08 | • Edit reply: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: 50b12dc4ba user: drh | |
| 11:07 | • Edit: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: 7d5c8b1923 user: drh | |
| 11:05 | • Reply: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: e48a97787b user: drh | |
| 10:48 | • Reply: can we use a for/while loop inside sqlite triggers ? artifact: 43f7bd720e user: anonymous | |
| 09:22 | • Reply: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: dca2fcf098 user: kmedcalf | |
| 08:06 | • Reply: SQLite.Interop.dll: Exception 0xc00000fd artifact: caecf8ec33 user: Flohack | |
| 07:18 | • Post: A stack overflow vulnerability in SQLite nmakehelp.c allows arbitrary code execution via a crated file artifact: 4a3625e733 user: salmonx | |
| 07:04 | • Post: A format string vulnerability in tool used to help build SQLite's TCL extension on Windows artifact: 7dcd751996 user: salmonx | |
| 06:21 | • Edit: can we use a for/while loop inside sqlite triggers ? artifact: 0f1552047e user: loki1993 | |
| 06:13 | • Post: can we use a for/while loop inside sqlite triggers ? artifact: 527fbc93ea user: loki1993 | |
| 04:39 | • Reply: Bug A NULL pointer dereference bug was discovered in SQLite artifact: ce1193be15 user: sqweek | |
| 04:00 | • Post: Bug A NULL pointer dereference bug was discovered in SQLite artifact: 48d46020bb user: salmonx | |
| 02:40 | • Reply: Extract files from sqlar with a directory prepended artifact: ee2c06e599 user: lexfiend | |
5 Years Ago (more context)
|
2020-06-15
| ||
| 22:02 | • Reply: New Caveat (bug?) Interrupt does not Interrupt during Columnar output artifact: ccc09a12a8 user: kmedcalf | |
| 21:18 | • Reply: New Caveat (bug?) Interrupt does not Interrupt during Columnar output artifact: 18bd898104 user: TripeHound | |
| 20:39 | • Reply: SetPassword no longer supported artifact: 09bb8e9c3a user: anonymous | |
| 19:17 | • Reply: Database change counter in WAL mode artifact: ca055f9bd3 user: anonymous | |
| 19:10 | • Reply: Bug?: CREATE TABLE with unsatisfied FK and DROP TABLE results in Error artifact: 606ab73b41 user: martinrode | |
| 18:28 | • Reply: SetPassword no longer supported artifact: 7a405a9e7f user: wyoung | |
| 18:26 | • Post: New Caveat (bug?) Interrupt does not Interrupt during Columnar output artifact: f283c9615f user: kmedcalf | |
| 18:06 | • Post: SetPassword no longer supported artifact: 487140a927 user: anonymous | |
| 17:51 | • Reply: ALTER TABLE new_X RENAME TO X issue. artifact: 20c333fb49 user: anonymous | |
| 16:50 | • Reply: DROP VIEW IF EXISTS failure artifact: 4e197179df user: TripeHound | |
| 16:45 | • Delete reply: DROP VIEW IF EXISTS failure artifact: 3c2b00e9e0 user: TripeHound | |
| 16:40 | • Reply: ALTER TABLE new_X RENAME TO X issue. artifact: f9f4ece6a5 user: LarryBrasfield | |
| 16:32 | • Reply: DROP VIEW IF EXISTS failure artifact: 681b89ebda user: kmedcalf | |
| 16:31 | • Reply: A question about the "type" field in the result of PRAGMA table_xinfo for the generated column. artifact: e14d67992d user: ChirsL | |
| 16:12 | • Reply: ALTER TABLE new_X RENAME TO X issue. artifact: 74516c17f2 user: ChirsL | |
| 16:06 | • Reply: A question about the "type" field in the result of PRAGMA table_xinfo for the generated column. artifact: 646a7d7b7d user: LarryBrasfield | |
| 15:52 | • Reply: ALTER TABLE new_X RENAME TO X issue. artifact: 1813977c23 user: TripeHound | |
| 15:44 | • Reply: A question about the "type" field in the result of PRAGMA table_xinfo for the generated column. artifact: 2ae084b385 user: drh | |
| 15:24 | • Edit reply: ALTER TABLE new_X RENAME TO X issue. artifact: 17cfe7535c user: LarryBrasfield | |
| 15:22 | • Reply: ALTER TABLE new_X RENAME TO X issue. artifact: fa667cc420 user: LarryBrasfield | |
| 15:07 | • Reply: A question about the "type" field in the result of PRAGMA table_xinfo for the generated column. artifact: 757815930e user: LarryBrasfield | |
| 13:58 | • Post: ALTER TABLE new_X RENAME TO X issue. artifact: 677649be1c user: ChirsL | |
| 08:26 | • Post: A question about the "type" field in the result of PRAGMA table_xinfo for the generated column. artifact: 102fb8fa37 user: ChirsL | |
| 08:21 | • Edit: (Deleted) artifact: 34a2b0f758 user: ChirsL | |
| 08:19 | • Post: (Deleted) artifact: cecce7ae6d user: ChirsL | |
| 07:36 | • Reply: DROP VIEW IF EXISTS failure artifact: 96d25c2b12 user: TripeHound | |
| 07:07 | • Reply: DROP VIEW IF EXISTS failure artifact: 5aee6f038c user: anonymous | |
| 06:51 | • Post: configure --enable-update-limit doesn't work. artifact: f96f079f5b user: shawnw | |
| 05:42 | • Reply: The word 'STORED' not show up in the lang_keywords.html page. artifact: 9b020fbab7 user: anonymous | |
| 02:18 | • Reply: DROP VIEW IF EXISTS failure artifact: 91769c9451 user: younique | |