Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent forum posts
|
2023-04-01
| ||
| 18:32 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 34609785c6 user: hanche) | |
| 16:29 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 1900f0265d user: spindrift) | |
| 15:33 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: b5b77f8f4f user: drh) | |
| 15:10 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: aeac304503 user: wyoung) | |
| 14:28 | • Edit: Feature Request: Support Binary representation like 0b01 (artifact: ce9d14f512 user: DenisTRUFFAUT) | |
| 10:42 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: b239b3fb6c user: hanche) | |
| 09:55 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 55284333b9 user: anonymous) | |
| 09:08 | • Post: Documentation Parsed one-liner from the `INSERT INTO ${table} VALUES( ... );` description (artifact: 5b4bfb834e user: anonymous) | |
| 08:12 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: b4df4c3a65 user: anonymous) | |
| 06:20 | • Edit reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 5b1d64b74a user: spindrift) | |
| 06:20 | • Edit reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 11882b29ec user: spindrift) | |
| 06:19 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 5e63a1607c user: spindrift) | |
|
2023-03-31
| ||
| 21:39 | • Reply: Feature request: Stored Procedures (artifact: 8acd04d7a0 user: nuclight) | |
| 20:58 | • Edit: Feature Request: Support Binary representation like 0b01 (artifact: 38b08e5db7 user: DenisTRUFFAUT) | |
| 20:56 | • Post: Feature Request: Support Binary representation like 0b01 (artifact: 7d42d1da35 user: DenisTRUFFAUT) | |
| 20:44 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 6b3f8a5c63 user: bjoern) | |
| 17:49 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: c9d6875f56 user: anonymous) | |
| 17:11 | • Edit reply: SQLite Wasm for Safari And Firefox progress (artifact: 449ae66eb1 user: stephan) | |
| 16:04 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: e2d1a8e470 user: bjoern) | |
| 15:22 | • Reply: Error when trying to add a column (Error checking foreign keys after table modification) (artifact: 6c7c5c20a5 user: anonymous) | |
| 14:38 | • Reply: Say how to get length(x) in bytes, not just characters, for strings (artifact: 670f8775d3 user: kmedcalf) | |
| 12:54 | • Reply: Say how to get length(x) in bytes, not just characters, for strings (artifact: 544ad083e8 user: jicman) | |
| 11:42 | • Reply: Optimizing JSON filter by syntheszing a LIKE (artifact: 538a0fea78 user: anonymous) | |
| 10:26 | • Post: Optimizing JSON filter by syntheszing a LIKE (artifact: 607099b02c user: anonymous) | |
| 09:08 | • Reply: Correct way of carrying connections over forked processes (artifact: 7ee948995a user: sqweek) | |
| 08:27 | • Reply: before insert trigger (artifact: c4cae44460 user: justme) | |
| 05:40 | • Reply: Correct way of carrying connections over forked processes (artifact: 209d409a23 user: larrybr) | |
| 05:35 | • Reply: Correct way of carrying connections over forked processes (artifact: b6f253e4bc user: paulclinger) | |
| 05:03 | • Reply: Correct way of carrying connections over forked processes (artifact: 5dd58a8cfa user: paulclinger) | |
| 04:25 | • Reply: Say how to get length(x) in bytes, not just characters, for strings (artifact: 2a2f9095c0 user: larrybr) | |
| 03:39 | • Reply: Correct way of carrying connections over forked processes (artifact: 6610956ad3 user: sqweek) | |
| 02:52 | • Reply: Say how to get length(x) in bytes, not just characters, for strings (artifact: c30514ac17 user: little-brother) | |
| 01:14 | • Post: Say how to get length(x) in bytes, not just characters, for strings (artifact: c0dd2100b2 user: jidanni) | |
|
2023-03-30
| ||
| 23:49 | • Reply: System.Data.SQLite transaction behaviour. (artifact: 1a319d8618 user: mistachkin) | |
| 23:12 | • Reply: Error: in prepare, no such column: %03d SQLite version 3.41.2 2023-03-22 11:56:21 (artifact: cfaa9a4ee0 user: knu) | |
| 22:41 | • Reply: Error: in prepare, no such column: %03d SQLite version 3.41.2 2023-03-22 11:56:21 (artifact: 5c40f49477 user: dempson) | |
| 22:24 | • Reply: before insert trigger (artifact: 59cb085a27 user: knu) | |
| 21:47 | • Reply: before insert trigger (artifact: eb6b942cff user: dfgriggs) | |
| 20:34 | • Reply: Error: in prepare, no such column: %03d SQLite version 3.41.2 2023-03-22 11:56:21 (artifact: 3ac2059ce5 user: knu) | |
| 18:47 | • Reply: unixepoch(): document if it rounds or truncates (artifact: 914f658ac2 user: larrybr) | |
| 18:08 | • Reply: Correct way of carrying connections over forked processes (artifact: 0f7a7b785d user: larrybr) | |
| 17:55 | • Edit: System.Data.SQLite transaction behaviour. (artifact: 364a5bfadf user: tolgaong) | |
| 17:51 | • Reply: before insert trigger (artifact: 9730496d99 user: justme) | |
| 17:39 | • Reply: Correct way of carrying connections over forked processes (artifact: d2ecd6cdcf user: paulclinger) | |
| 17:38 | • Reply: before insert trigger (artifact: 38c117a6b2 user: dvdraymond) | |
| 17:30 | • Reply: Correct way of carrying connections over forked processes (artifact: 86f3267e20 user: paulclinger) | |
| 17:24 | • Reply: Correct way of carrying connections over forked processes (artifact: b5f8e9fe70 user: paulclinger) | |
| 17:19 | • Reply: Correct way of carrying connections over forked processes (artifact: a4eab4245a user: paulclinger) | |
| 17:17 | • Reply: before insert trigger (artifact: e88f7361b4 user: dvdraymond) | |
| 17:04 | • Reply: why does this query return table names instead of actual tables? (artifact: 202cf263de user: sqlitevexee) | |