This Day In History For 2023-07-15
1 Year Ago (more context)
|
2022-07-15
| ||
| 21:29 | • Reply: REGEXP (X) bug artifact: 18f87fdcdf user: scandariato | |
| 21:08 | • Reply: Trigger order help artifact: 6de4cb9a2b user: pcreso | |
| 20:29 | • Reply: REGEXP X{m,n} bug artifact: 57cbaf1d0e user: larrybr | |
| 20:29 | • Reply: REGEXP X{m,n} bug artifact: 237b2a7c8e user: scandariato | |
| 20:19 | • Reply: REGEXP X{m,n} bug artifact: d823541e3d user: stephan | |
| 20:17 | • Reply: Trigger order help artifact: 80602df6c9 user: pcreso | |
| 20:12 | • Reply: REGEXP X{m,n} bug artifact: f6a7a16fac user: larrybr | |
| 19:53 | • Reply: REGEXP X{m,n} bug artifact: 61a2b9855e user: jchd18 | |
| 19:42 | • Edit: REGEXP (X) bug artifact: 0d6a9160f8 user: scandariato | |
| 19:36 | • Post: REGEXP (X) bug artifact: 8996f5757c user: scandariato | |
| 19:24 | • Reply: REGEXP X{m,n} bug artifact: ead2949d0f user: scandariato | |
| 18:57 | • Reply: REGEXP X{m,n} bug artifact: e135fab6a1 user: jchd18 | |
| 18:21 | • Reply: The URI parser doesn't handle spaces encoded as plus characters in parameters artifact: f465f90b0c user: larrybr | |
| 18:15 | • Reply: REGEXP X{m,n} bug artifact: 44de87e5bd user: stephan | |
| 17:51 | • Reply: The URI parser doesn't handle spaces encoded as plus characters in parameters artifact: 8a38059dcb user: vman59 | |
| 17:51 | • Reply: possible to use DISTINCT with wildcard? artifact: 4628b7008e user: dvdraymond | |
| 17:23 | • Reply: The URI parser doesn't handle spaces encoded as plus characters in parameters artifact: 5b60cd86aa user: lexfiend | |
| 16:06 | • Post: possible to use DISTINCT with wildcard? artifact: cc83b993d7 user: chovyfu | |
| 15:25 | • Post: REGEXP X{m,n} bug artifact: 8694e55a2c user: scandariato | |
| 12:59 | • Reply: Assertion `pRec->nField>0 && pRec->nField<=pIdx->nSampleCol' failed. artifact: f184825331 user: drh | |
| 09:59 | • Reply: Trigger order help artifact: 26b26202cf user: slavin | |
| 09:20 | • Reply: Trigger order help artifact: b31646f204 user: anonymous | |
| 02:52 | • Post: Assertion `pRec->nField>0 && pRec->nField<=pIdx->nSampleCol' failed. artifact: 3607259d3c user: bajinsheng | |
| 02:43 | • Post: Trigger order help artifact: bf99e8682a user: pcreso | |
| 01:27 | • Post: The URI parser doesn't handle spaces encoded as plus characters in parameters artifact: b260eec8af user: anonymous | |
| 00:19 | • Reply: Unexpected Result by NULL AS NUMBERIC artifact: c777f8a29b user: bajinsheng | |
2 Years Ago (more context)
|
2021-07-15
| ||
| 23:57 | • Reply: Should SQLite be able to optimize this query? artifact: 19acdf0b27 user: cuz | |
| 23:29 | • Edit reply: Should SQLite be able to optimize this query? artifact: 062d576715 user: drh | |
| 23:27 | • Reply: Should SQLite be able to optimize this query? artifact: f7f6637918 user: drh | |
| 22:24 | • Reply: More math help and what I've learned artifact: e9f8970374 user: ThanksRyan | |
| 21:04 | • Reply: Help with a query artifact: 0b0aea8efc user: anonymous | |
| 19:51 | • Reply: Should SQLite be able to optimize this query? artifact: acac0c5cb7 user: anonymous | |
| 19:51 | • Reply: Should SQLite be able to optimize this query? artifact: c2d8faf656 user: larrybr | |
| 19:45 | • Reply: Should SQLite be able to optimize this query? artifact: 8ada395a25 user: simonw | |
| 19:34 | • Reply: Should SQLite be able to optimize this query? artifact: 8c0a5f40fb user: drh | |
| 18:29 | • Post: PSTOKEN extension (new version) artifact: 0e2bc16832 user: anonymous | |
| 18:23 | • Reply: Should SQLite be able to optimize this query? artifact: 3344977a85 user: dvdraymond | |
| 18:06 | • Reply: Should SQLite be able to optimize this query? artifact: 5f119f0dff user: drh | |
| 17:52 | • Reply: Should SQLite be able to optimize this query? artifact: 0212439555 user: simonw | |
| 17:18 | • Reply: Should SQLite be able to optimize this query? artifact: fffb9616bd user: drh | |
| 16:44 | • Reply: More math help and what I've learned artifact: 344358f4c1 user: RoboManni | |
| 16:40 | • Reply: Should SQLite be able to optimize this query? artifact: 5d14ed56db user: simonw | |
| 16:32 | • Reply: Should SQLite be able to optimize this query? artifact: 466c8fec3b user: simonw | |
| 16:31 | • Reply: Should SQLite be able to optimize this query? artifact: 91c56240d2 user: simonw | |
| 16:25 | • Reply: Should SQLite be able to optimize this query? artifact: 0fc6dcfcf7 user: drh | |
| 16:16 | • Reply: Should SQLite be able to optimize this query? artifact: 25a5c5b395 user: mzm2021 | |
| 16:07 | • Post: Should SQLite be able to optimize this query? artifact: 2d76f2bcf6 user: simonw | |
| 15:40 | • Reply: Feature request: add index info to WITH clause table artifact: 65b5b446b8 user: RoboManni | |
| 15:12 | • Reply: More math help and what I've learned artifact: 2f0e851a25 user: ThanksRyan | |
| 14:22 | • Edit reply: Feature request: add index info to WITH clause table artifact: b269164623 user: mzm2021 | |
| 14:20 | • Reply: Feature request: add index info to WITH clause table artifact: 00fbd81e67 user: mzm2021 | |
| 13:46 | • Reply: FILTER clause with window functions artifact: 8691e0dbab user: anonymous | |
| 12:56 | • Reply: Feature request: add index info to WITH clause table artifact: 47e359f7ec user: dvdraymond | |
| 12:39 | • Reply: Help with a query artifact: d8042e7a64 user: larrybr | |
| 11:33 | • Reply: Help with a query artifact: aa167badc2 user: anonymous | |
| 11:30 | • Edit: Feature request: add index info to WITH clause table artifact: 74cbdcafc0 user: RoboManni | |
| 11:29 | • Edit: Feature request: add index info to WITH clause table artifact: 0532d5bb8a user: RoboManni | |
| 11:27 | • Post: Feature request: add index info to WITH clause table artifact: 0c3edab209 user: RoboManni | |
| 11:03 | • Reply: Custom error messages for required table-valued function parameter artifact: bce87eaf56 user: drh | |
| 10:46 | • Reply: Help with a query artifact: 06b0fa9016 user: hanche | |
| 04:01 | • Reply: Custom error messages for required table-valued function parameter artifact: d4556ea17c user: dmatson | |
3 Years Ago (more context)
|
2020-07-15
| ||
| 23:58 | • Reply: how to check update statement really modify a record artifact: 9bc993e320 user: stephan | |
| 23:16 | • Reply: how to check update statement really modify a record artifact: c6f664ae6f user: kmedcalf | |
| 22:59 | • Reply: how to check update statement really modify a record artifact: 7c0e18a2e4 user: kmedcalf | |
| 21:26 | • Reply: how to check update statement really modify a record artifact: 4048b0f09e user: slavin | |
| 20:24 | • Post: UPDATE in version 3.33 artifact: fe59966950 user: anonymous | |
| 17:47 | • Reply: how to check update statement really modify a record artifact: ced02be52d user: dvdraymond | |
| 17:40 | • Reply: how to check update statement really modify a record artifact: c7d049eb72 user: stephan | |
| 17:32 | • Reply: System.Data.SQLite.Core for .Net artifact: 36bc5f5fb2 user: stephan | |
| 17:31 | • Reply: how to check update statement really modify a record artifact: 9d7e6cfbe1 user: cuz | |
| 17:11 | • Post: System.Data.SQLite.Core for .Net artifact: 91b8524eb5 user: nandostyle | |
| 16:58 | • Reply: Endianness help artifact: 30f2c372d9 user: curmudgeon | |
| 14:53 | • Reply: how to check update statement really modify a record artifact: 51b803fa78 user: stephan | |
| 14:46 | • Reply: how to check update statement really modify a record artifact: fec968b57c user: doug9forester | |
| 14:38 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 8845210cdb user: kmedcalf | |
| 13:41 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: e056d99e9f user: JohnSmith | |
| 13:06 | • Reply: Arithmetic errors artifact: 929ee73f6d user: kmedcalf | |
| 12:48 | • Reply: Arithmetic errors artifact: c73f89c367 user: wyoung | |
| 12:46 | • Reply: how to check update statement really modify a record artifact: ba33530f58 user: slavin | |
| 12:20 | • Reply: Arithmetic errors artifact: 932d1d7f0c user: anonymous | |
| 11:37 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 983468a6d2 user: kmedcalf | |
| 11:18 | • Reply: Arithmetic errors artifact: 3400062664 user: kmedcalf | |
| 08:45 | • Reply: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: eca0e5f1d1 user: TripeHound | |
| 07:14 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 5bbd5b68c8 user: JohnSmith | |
| 05:56 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: d2d81b46bc user: kmedcalf | |
| 05:46 | • Post: Arithmetic errors artifact: 34fb87e896 user: anonymous | |
| 04:53 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 2f3534de1f user: anonymous | |
| 04:16 | • Reply: When using sqlite3_step(stmt) inside a transaction my busy-handler is not being called artifact: 4643da3e5a user: JohnSmith | |
| 02:30 | • Edit reply: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: 5d5b6a6414 user: Yiting | |
| 02:29 | • Reply: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: 452611cda0 user: drh | |
| 01:59 | • Reply: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: b60a8aec7b user: Yiting | |
| 01:50 | • Reply: how to check update statement really modify a record artifact: 7f9cfd47e9 user: XiongZaiBingGan | |
| 01:47 | • Reply: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: 14ff6231ec user: drh | |
| 01:42 | • Post: The SQLITE_DETERMINISTIC flag isn't work on 3.32.3 release artifact: 10133f99de user: Yiting | |
| 01:34 | • Reply: how to check update statement really modify a record artifact: 42983a91e0 user: XiongZaiBingGan | |
| 01:33 | • Reply: how to check update statement really modify a record artifact: d072f9bac1 user: XiongZaiBingGan | |