Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 events by user kmedcalf occurring around 2021-07-12 23:41:51.
2021-07-19
| ||
20:05 | • Reply: Unexpected return from the NULL column artifact: 7823fbd6e6 user: kmedcalf | |
18:58 | • Edit reply: Unexpected return from the NULL column artifact: a46c91af8c user: kmedcalf | |
18:56 | • Reply: Unexpected return from the NULL column artifact: 48cc1c7c6b user: kmedcalf | |
18:19 | • Reply: LIKE optimization - limitation to string literals artifact: 5eed38ae42 user: kmedcalf | |
2021-07-18
| ||
23:11 | • Reply: LIKE optimization - limitation to string literals artifact: 5e068b8c49 user: kmedcalf | |
22:56 | • Reply: LIKE optimization - limitation to string literals artifact: 8986c8ea97 user: kmedcalf | |
20:49 | • Reply: Inserting One Billion Rows in SQLite Under A Minute artifact: b31eff149e user: kmedcalf | |
20:38 | • Reply: Does the column order in an insert statement impact the insert speed? artifact: 28c2401f3c user: kmedcalf | |
20:21 | • Reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 94128a21c8 user: kmedcalf | |
20:08 | • Reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 02f7bda329 user: kmedcalf | |
00:41 | • Edit reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 550045447f user: kmedcalf | |
00:23 | • Reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 44e29996b7 user: kmedcalf | |
2021-07-17
| ||
23:41 | • Edit reply: ORDER BY not ordering with the correct result artifact: aa0ebe26ed user: kmedcalf | |
23:39 | • Reply: ORDER BY not ordering with the correct result artifact: 5c3f79cffa user: kmedcalf | |
23:25 | • Reply: (Deleted) artifact: 9d6c41b5fa user: kmedcalf | |
23:09 | • Reply: (Deleted) artifact: 78d0c6a2a3 user: kmedcalf | |
22:52 | • Reply: ORDER BY not ordering with the correct result artifact: 113c5d7b16 user: kmedcalf | |
22:29 | • Reply: (Deleted) artifact: c08eb1e306 user: kmedcalf | |
22:25 | • Reply: (Deleted) artifact: a956b84d82 user: kmedcalf | |
22:20 | • Reply: Tips for getting SQLite under Python to perform better with more RAM? artifact: 219a431b5d user: kmedcalf | |
21:44 | • Reply: (Deleted) artifact: 23fc511d83 user: kmedcalf | |
21:38 | • Reply: ORDER BY not ordering with the correct result artifact: b02e7f161a user: kmedcalf | |
2021-07-13
| ||
00:38 | • Reply: CHECK and ON CONFLICT artifact: ec02265fb3 user: kmedcalf | |
00:27 | • Reply: What join is needed for non-similar data? artifact: 7459a2b393 user: kmedcalf | |
2021-07-12
| ||
23:41 | • Edit reply: How much would you trust a page-level checksum ? artifact: fc577eb803 user: kmedcalf | |
23:36 | • Reply: How much would you trust a page-level checksum ? artifact: 1468cbc367 user: kmedcalf | |
22:14 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 4ba5fe1656 user: kmedcalf | |
21:55 | • Edit reply: How much would you trust a page-level checksum ? artifact: be9a5dad32 user: kmedcalf | |
21:53 | • Reply: How much would you trust a page-level checksum ? artifact: ec10000b20 user: kmedcalf | |
2021-07-11
| ||
22:25 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 499f52aa70 user: kmedcalf | |
22:22 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 8f99ed3223 user: kmedcalf | |
22:05 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 764065ab63 user: kmedcalf | |
22:01 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 53216b2928 user: kmedcalf | |
20:53 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 50fc0d0a3d user: kmedcalf | |
20:40 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 1c2fbbfae9 user: kmedcalf | |
20:38 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: c2bae8c59b user: kmedcalf | |
20:36 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: f24446aa83 user: kmedcalf | |
20:24 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: 63ac2b56d2 user: kmedcalf | |
19:50 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: c9da49bb23 user: kmedcalf | |
19:38 | • Edit reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: b23c3d34a0 user: kmedcalf | |
19:36 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: bcfaddd2d3 user: kmedcalf | |
18:43 | • Reply: is it possible to update bunch of records in reverse order to avoid unique constrain violation artifact: d53b0b1412 user: kmedcalf | |
2021-07-10
| ||
18:05 | • Reply: Can this SQL be simplified? artifact: 3faafc8a11 user: kmedcalf | |
18:04 | • Reply: Can this SQL be simplified? artifact: bf0829e919 user: kmedcalf | |
16:55 | • Delete reply: Why can you write triggers using functions from extensions? How does that work? artifact: 5ec4cab66a user: kmedcalf | |
16:52 | • Reply: Why can you write triggers using functions from extensions? How does that work? artifact: 8f2b52a006 user: kmedcalf | |
2021-07-09
| ||
22:05 | • Reply: How to handle collation version changes artifact: 5317344555 user: kmedcalf | |
21:24 | • Reply: Linkage #defines are unused artifact: 7bc94de9ec user: kmedcalf | |
09:09 | • Reply: Deleted rows not in FreeList artifact: 208177b00a user: kmedcalf | |
07:28 | • Reply: Gimme my options! a feature to be artifact: bd318ecf72 user: kmedcalf | |