This Day In History For 2023-07-16
1 Year Ago (more context)
|
2022-07-16
| ||
| 23:14 | • Reply: sqlite3 Browser unwarranted syntax error defining trigger artifact: 62cdc65130 user: larrybr | |
| 23:00 | • Reply: sqlite3 Browser unwarranted syntax error defining trigger artifact: 6f87a341b8 user: anonymous | |
| 21:21 | • Reply: Backup via file system backup software artifact: c56e94c016 user: ve3meo | |
| 19:23 | • Reply: Why doesn't negative rounding (very useful for binning) work for sqlite3 in the Pandas read_sql_query() function? artifact: ff387d22e6 user: kmedcalf | |
| 19:08 | • Edit reply: Why doesn't negative rounding (very useful for binning) work for sqlite3 in the Pandas read_sql_query() function? artifact: 8642e05c2e user: kmedcalf | |
| 19:02 | • Reply: Why doesn't negative rounding (very useful for binning) work for sqlite3 in the Pandas read_sql_query() function? artifact: 312056622b user: kmedcalf | |
| 18:50 | • Reply: Why doesn't negative rounding (very useful for binning) work for sqlite3 in the Pandas read_sql_query() function? artifact: 72bf60aec1 user: larrybr | |
| 16:49 | • Post: Why doesn't negative rounding (very useful for binning) work for sqlite3 in the Pandas read_sql_query() function? artifact: 6b4c4cdfcb user: ghayward | |
| 15:48 | • Reply: sqlite3 Browser not listing all defined triggers artifact: ec81f95dfc user: stephan | |
| 15:30 | • Reply: sqlite3 Browser unwarranted syntax error defining trigger artifact: fd31e5395b user: stephan | |
| 15:24 | • Post: sqlite3 Browser not listing all defined triggers artifact: 99d851a8b6 user: anonymous | |
| 15:13 | • Post: sqlite3 Browser unwarranted syntax error defining trigger artifact: 5062af3619 user: anonymous | |
| 14:35 | • Reply: max() function broken artifact: 755af23c7b user: knu | |
| 14:17 | • Reply: RSS feed for news artifact: dfefb0d4c1 user: knu | |
| 13:21 | • Post: max() function broken artifact: 4e1de86205 user: SunnySaini_com | |
| 11:32 | • Post: RSS feed for news artifact: c453d4ff84 user: anonymous | |
| 05:01 | • Reply: Trigger order help artifact: 679bff145e user: pcreso | |
| 02:09 | • Reply: Trigger order help artifact: 0578f798fb user: slavin | |
| 00:35 | • Reply: The URI parser doesn't handle spaces encoded as plus characters in parameters artifact: 5dfcc9c230 user: anonymous | |
2 Years Ago (more context)
|
2021-07-16
| ||
| 23:58 | • Reply: operator precedence docs missing, suggested clarifications below artifact: dae3913bd7 user: rmariani | |
| 23:56 | • Edit: operator precedence docs missing, suggested clarifications below artifact: 646f8e2b0f user: rmariani | |
| 23:54 | • Reply: operator precedence docs missing, suggested clarifications below artifact: 0fa3e125c2 user: rmariani | |
| 23:45 | • Post: operator precedence docs missing, suggested clarifications below artifact: bdecd53c40 user: rmariani | |
| 22:51 | • Reply: Should SQLite be able to optimize this query? artifact: 878ca7a9be user: drh | |
| 22:18 | • Edit: (Deleted) artifact: 049fdec4e1 user: Trudge | |
| 21:42 | • Post: (Deleted) artifact: d659cd362a user: Trudge | |
| 19:46 | • Edit reply: Should SQLite be able to optimize this query? artifact: f6901a235d user: drh | |
| 19:40 | • Edit reply: Should SQLite be able to optimize this query? artifact: f9df43adb5 user: drh | |
| 19:38 | • Reply: Should SQLite be able to optimize this query? artifact: 4a76777e6d user: drh | |
| 19:05 | • Reply: Should SQLite be able to optimize this query? artifact: 6be1468b85 user: drh | |
| 18:56 | • Reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 2c9c5ae773 user: anonymous | |
| 18:41 | • Edit: Tips for getting SQLite under Python to perform better with more RAM? artifact: 9a6b9ae8e2 user: simonw | |
| 18:40 | • Edit: Tips for getting SQLite under Python to perform better with more RAM? artifact: f6bdd6b503 user: simonw | |
| 18:26 | • Reply: Should SQLite be able to optimize this query? artifact: faf982aced user: simonw | |
| 18:23 | • Post: Tips for getting SQLite under Python to perform better with more RAM? artifact: 9e15765874 user: simonw | |
| 18:03 | • Reply: Documentation typo in Retrieving Statement SQL artifact: 13d61eadd2 user: larrybr | |
| 18:02 | • Post: cycle detection in CHECK constraint with recursive CTE artifact: 621a2129b5 user: anonymous | |
| 17:34 | • Post: PCRE as an optionally core extension? artifact: 3bf4913d27 user: guillaume | |
| 17:27 | • Reply: Custom error messages for required table-valued function parameter artifact: c83977a7e6 user: drh | |
| 16:30 | • Reply: Should SQLite be able to optimize this query? artifact: bbb2a464ae user: larrybr | |
| 15:18 | • Reply: Memory cache artifact: c11a064a0d user: levente | |
| 15:05 | • Reply: Should SQLite be able to optimize this query? artifact: 442c21d1d2 user: drh | |
| 14:14 | • Post: Documentation typo in Retrieving Statement SQL artifact: 23a98d2b51 user: anonymous | |
| 13:18 | • Reply: Help with a query artifact: dbb97b177a user: larrybr | |
| 12:31 | • Edit: Clear shared memory DB and backup problem artifact: 6cdaf350a6 user: rexopl | |
| 12:30 | • Reply: Memory cache artifact: 18284fd11b user: rexopl | |
| 12:06 | • Post: Clear shared memory DB and backup problem artifact: 6d2624dd78 user: rexopl | |
| 11:50 | • Reply: Whole grammar railroad diagram artifact: ae56be81ee user: mingodad | |
| 09:12 | • Reply: Help with a query artifact: 04900a8152 user: anonymous | |
| 09:04 | • Reply: Whole grammar railroad diagram artifact: eb514e05be user: mingodad | |
| 08:19 | • Reply: Memory cache artifact: ae9c105798 user: anonymous | |
| 07:08 | • Post: Memory cache artifact: 339ed9ff91 user: levente | |
| 07:08 | • Reply: More math help and what I've learned artifact: 34e0195277 user: RoboManni | |
| 06:44 | • Reply: Should SQLite be able to optimize this query? artifact: dcea280c08 user: RoboManni | |
| 05:58 | • Reply: Should SQLite be able to optimize this query? artifact: 445f8007b4 user: gunter_hick | |
| 03:45 | • Reply: Should SQLite be able to optimize this query? artifact: 8d1660e7ee user: anonymous | |
| 01:50 | • Reply: Should SQLite be able to optimize this query? artifact: 6ecf3cab23 user: simonw | |
| 01:22 | • Reply: Should SQLite be able to optimize this query? artifact: e071e0991f user: drh | |
3 Years Ago (more context)
|
2020-07-16
| ||
| 20:40 | • Reply: SELECT using variables artifact: 5cd84a92cb user: LarryBrasfield | |
| 20:28 | • Post: SELECT using variables artifact: f4cf2b30c8 user: anonymous | |
| 20:04 | • Reply: SQLITE_HAS_CODE is gone? artifact: 597cb33cc7 user: wyoung | |
| 19:50 | • Reply: SQLITE_HAS_CODE is gone? artifact: bdf1defeb8 user: jchd18 | |
| 19:18 | • Reply: SQLITE_HAS_CODE is gone? artifact: 8062cdcd1b user: wyoung | |
| 19:05 | • Reply: SQLITE_HAS_CODE is gone? artifact: 2c5d8f6203 user: wyoung | |
| 18:56 | • Reply: SQLITE_HAS_CODE is gone? artifact: 9bcbf50147 user: jchd18 | |
| 18:47 | • Edit reply: how to check update statement really modify a record artifact: 446684b1f3 user: kmedcalf | |
| 18:46 | • Reply: how to check update statement really modify a record artifact: c10b16a491 user: dvdraymond | |
| 18:06 | • Reply: how to check update statement really modify a record artifact: 0744dd81dc user: stephan | |
| 17:58 | • Reply: Possible bug in .read when a directory is specified? artifact: 7a10ca518d user: stephan | |
| 17:50 | • Post: Possible bug in .read when a directory is specified? artifact: 4c53c434ca user: lcarlp | |
| 17:48 | • Reply: how to check update statement really modify a record artifact: cf1a8a06e8 user: doug9forester | |
| 17:40 | • Reply: how to check update statement really modify a record artifact: 574c8b134d user: kmedcalf | |
| 17:07 | • Reply: how to check update statement really modify a record artifact: 49284abed2 user: stephan | |
| 17:00 | • Reply: how to check update statement really modify a record artifact: 1b91a349e0 user: cuz | |
| 16:18 | • Reply: how to check update statement really modify a record artifact: c7ab1357f2 user: stephan | |
| 16:03 | • Reply: how to check update statement really modify a record artifact: b7913b7ad0 user: cuz | |
| 15:37 | • Reply: UPDATE in version 3.33 artifact: 00ab2253aa user: kmedcalf | |
| 13:37 | • Reply: Access sqlite database from user function artifact: 92fb1fa2e8 user: kmedcalf | |
| 13:18 | • Reply: UPDATE in version 3.33 artifact: d970a97db7 user: kmedcalf | |
| 09:05 | • Reply: Missing link in SQL documentation root to transaction artifact: 8afb66b028 user: anonymous | |
| 07:38 | • Post: Access sqlite database from user function artifact: 0865192e81 user: anonymous | |
| 07:34 | • Reply: Arithmetic errors artifact: a2f4b3f37f user: anonymous | |
| 06:26 | • Reply: UPDATE in version 3.33 artifact: 999a9d047f user: anonymous | |
| 04:34 | • Reply: UPDATE in version 3.33 artifact: 1dc831b0d2 user: dempson | |
| 04:29 | • Reply: facing issue from sqlite3_step() artifact: ae8e31863e user: kmedcalf | |
| 04:19 | • Edit reply: UPDATE in version 3.33 artifact: 41017a8da1 user: kmedcalf | |
| 04:15 | • Reply: UPDATE in version 3.33 artifact: f8d22cbae9 user: kmedcalf | |
| 03:46 | • Reply: facing issue from sqlite3_step() artifact: 7fc3597e03 user: itandetnik | |
| 02:40 | • Post: facing issue from sqlite3_step() artifact: d109f60409 user: prajeeshprakashp | |
| 02:33 | • Reply: PSTOKEN extension artifact: b1bd78c5e5 user: anonymous | |
| 02:10 | • Reply: how to check update statement really modify a record artifact: 1e8160d290 user: anonymous | |
| 01:59 | • Reply: UPDATE in version 3.33 artifact: f771fc8c47 user: anonymous | |