SQLite Forum

Timeline
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

50 events occurring around f88951d6b5f84d7f.

2020-12-27
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