Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
87 events occurring around e68575b51fc2a827.
|
2020-12-28
| ||
| 23:47 | • Reply: Missing comma in ctime.c (artifact: d2de04cf31 user: LarryBrasfield) | |
| 23:00 | • Reply: Suggestion: Use strong hashes on the download page (artifact: 05c1fa3e4e user: drh) | |
| 22:18 | • Reply: Suggestion: Use strong hashes on the download page (artifact: 6f9048626c user: kmedcalf) | |
| 22:07 | • Reply: Missing comma in ctime.c (artifact: ab086d0def user: rillig) | |
| 21:43 | • Reply: Suggestion: Use strong hashes on the download page (artifact: ac29b8f0f5 user: anonymous) | |
| 21:36 | • Edit reply: Off-by-one in testing.html (artifact: 0ff5a77a45 user: kmedcalf) | |
| 21:32 | • Reply: Off-by-one in testing.html (artifact: f028ae2534 user: kmedcalf) | |
| 21:11 | • Post: Missing comma in ctime.c (artifact: aacac97680 user: kmedcalf) | |
| 19:05 | • Reply: Off-by-one in testing.html (artifact: 2383d81107 user: RichardDamon) | |
| 18:21 | • Reply: Off-by-one in testing.html (artifact: 9c38a1e92c user: wyoung) | |
| 10:47 | • Reply: DbStat via JDBC (artifact: 3ced7a6725 user: curmudgeon) | |
| 09:32 | • Post: DbStat via JDBC (artifact: 152bb9e71b user: dprutean) | |
| 08:39 | • Reply: Huge WAL file, but not for the usual reasons (artifact: 9f902733f5 user: relatively_random) | |
| 03:10 | • Reply: on conflict depends on conflict (artifact: a3ea04d182 user: kmedcalf) | |
| 02:53 | • Edit reply: on conflict depends on conflict (artifact: f80a710938 user: kmedcalf) | |
| 02:49 | • Reply: on conflict depends on conflict (artifact: 5b7102a3b2 user: kmedcalf) | |
| 01:34 | • Post: on conflict depends on conflict (artifact: 6d558007a4 user: moskvich412) | |
| 00:58 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 8a2b77310b user: 1codedebugger) | |
| 00:26 | • Edit reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 2e890e6751 user: kmedcalf) | |
| 00:18 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: ada216320e user: kmedcalf) | |
|
2020-12-27
| ||
| 23:00 | • Reply: .timer on (artifact: 482b955cfc user: kmedcalf) | |
| 22:34 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: d82cc7f289 user: 1codedebugger) | |
| 22:29 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: f3d7bee10a user: kmedcalf) | |
| 22:29 | • Reply: .timer on (artifact: 385863c55d user: slavin) | |
| 22:23 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 59b89c270b user: 1codedebugger) | |
| 22:20 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: d34ca5b5ce user: kmedcalf) | |
| 22:13 | • Edit reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 71c54ab13e user: kmedcalf) | |
| 22:07 | • Edit reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: eca46565bf user: kmedcalf) | |
| 22:04 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: a4ab1774e2 user: kmedcalf) | |
| 21:35 | • Reply: .timer on (artifact: 20c102e438 user: anonymous) | |
| 21:22 | • Edit reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 3d4771cf05 user: kmedcalf) | |
| 21:19 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 9466132f15 user: kmedcalf) | |
| 20:49 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 588247dfec user: 1codedebugger) | |
| 20:45 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 2a68bbc400 user: kmedcalf) | |
| 20:20 | • Edit: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: e40f26fe68 user: 1codedebugger) | |
| 20:19 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 1362341e88 user: 1codedebugger) | |
| 19:28 | • Edit reply: .timer on (artifact: 7557803447 user: kmedcalf) | |
| 19:28 | • Edit reply: .timer on (artifact: cd791bd3d1 user: kmedcalf) | |
| 19:26 | • Edit reply: .timer on (artifact: 6f275f1756 user: kmedcalf) | |
| 19:18 | • Edit reply: .timer on (artifact: 1a7fc421a7 user: kmedcalf) | |
| 19:16 | • Reply: .timer on (artifact: 3f73899f94 user: kmedcalf) | |
| 17:55 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: a984723f32 user: anonymous) | |
| 17:18 | • Edit reply: sqlite-gui application (artifact: 3f69ab5d8b user: little-brother) | |
| 17:11 | • Reply: sqlite-gui application (artifact: 0cb56a5fe5 user: little-brother) | |
| 16:23 | • Post: .timer on (artifact: e68575b51f user: anonymous) | |
| 16:06 | • Reply: Joining table-valued functions with a dynamic constraint (artifact: 91e2715030 user: patrickdevivo) | |
| 14:27 | • Reply: sqlite-gui application (artifact: 380c88b185 user: anonymous) | |
| 11:29 | • Post: Off-by-one in testing.html (artifact: 5faa799aa2 user: anonymous) | |
| 10:08 | • Reply: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: f88951d6b5 user: cladisch) | |
| 08:32 | • Reply: sqlite-gui application (artifact: 23b709f688 user: little-brother) | |
| 08:11 | • Reply: Creating an emty database (artifact: ea70d6bb74 user: luuk) | |
| 02:47 | • Edit reply: Question about Multiple database connections and loadable extensions. (artifact: ddd21897a6 user: 1codedebugger) | |
|
2020-12-26
| ||
| 20:40 | • Delete reply: Interesting question: Why aren't you using SQLite more? (artifact: 161ca1d86f user: 1codedebugger) | |
| 19:35 | • Post: Is using prepared statements without a FROM to employ built-in methods bad practice? (artifact: 55a255cd76 user: 1codedebugger) | |
| 19:06 | • Reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: 3e2ba0f1b4 user: kmedcalf) | |
| 18:30 | • Reply: Question about Multiple database connections and loadable extensions. (artifact: d921d8fd9b user: 1codedebugger) | |
| 18:26 | • Reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: eb7b72da43 user: 1codedebugger) | |
| 18:18 | • Reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: 78e9c1ca65 user: 1codedebugger) | |
| 08:04 | • Reply: 3 incorrect tables created during import (artifact: 126c792c50 user: EricTsau) | |
| 02:54 | • Reply: Novice question about employing more complex SQL versus procedural code (artifact: 38231853d0 user: jake) | |
| 02:13 | • Edit reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: 9010d147c3 user: kmedcalf) | |
| 02:11 | • Reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: 3253d0d53b user: kmedcalf) | |
| 01:50 | • Reply: sqlite3_expanded_sql for carray with single bound parameter (artifact: 563e854657 user: jake) | |
| 01:24 | • Post: sqlite3_expanded_sql for carray with single bound parameter (artifact: 8bdeea68bd user: 1codedebugger) | |
| 01:18 | • Reply: Possible Bug - View behaves differently to Table in SELECT (artifact: 52e9c28ea4 user: dpratten) | |
| 01:16 | • Reply: Creating an emty database (artifact: 21fe8931dd user: RichardDamon) | |
| 01:11 | • Reply: Creating an emty database (artifact: 5f617e24e5 user: kmedcalf) | |
| 01:09 | • Reply: Possible Bug - View behaves differently to Table in SELECT (artifact: 2de12cf774 user: dpratten) | |
| 01:02 | • Reply: Novice question about employing more complex SQL versus procedural code (artifact: 4a90f17a99 user: kmedcalf) | |
| 00:57 | • Reply: Creating an emty database (artifact: f3ce5f2f96 user: stephan) | |
| 00:44 | • Post: Creating an emty database (artifact: 62ccd96175 user: oneeyeman) | |
| 00:19 | • Reply: Novice question about employing more complex SQL versus procedural code (artifact: 827409fe28 user: 1codedebugger) | |
|
2020-12-25
| ||
| 21:16 | • Reply: 3 incorrect tables created during import (artifact: 501070a68a user: kmedcalf) | |
| 20:58 | • Reply: 3 incorrect tables created during import (artifact: bbcf6bd5e2 user: kmedcalf) | |
| 20:28 | • Reply: 3 incorrect tables created during import (artifact: 4af0fe7c45 user: EricTsau) | |
| 19:57 | • Reply: Check date when not null (artifact: b07936a4b5 user: kmedcalf) | |
| 19:34 | • Reply: Check date when not null (artifact: 5b0887ebfb user: kmedcalf) | |
| 19:34 | • Edit reply: Check date when not null (artifact: 7e42b6fd52 user: kmedcalf) | |
| 19:30 | • Reply: Check date when not null (artifact: 472a6fae6a user: kmedcalf) | |
| 18:50 | • Edit reply: Check date when not null (artifact: 805f1e5687 user: kmedcalf) | |
| 18:03 | • Reply: Check date when not null (artifact: a586ad0da9 user: kmedcalf) | |
| 18:01 | • Reply: Simple COUNT/GROUP BY query using a temporary table (artifact: f0133fe491 user: JLHainaut) | |
| 13:24 | • Reply: Check date when not null (artifact: 195ddb0623 user: jking) | |
| 11:38 | • Post: Check date when not null (artifact: fefb83b658 user: CecilWesterhof) | |
| 11:18 | • Reply: Interesting question: Why aren't you using SQLite more? (artifact: 5106b1bd20 user: CecilWesterhof) | |
| 06:47 | • Reply: SQLITE_FCNTL_WIN32_GET_HANDLE (artifact: b3e4199bab user: anonymous) | |
| 06:39 | • Reply: Interesting question: Why aren't you using SQLite more? (artifact: 2b7dbae629 user: 1codedebugger) | |