nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqhg2hvzx6sxxrwkk5a90eskxm9qu00lw26faq8yvdukfv7295uz6sxwmcwl (nprofile…mcwl) This is not yet exposed by Diesel, but I would happily merge a PR adding support for it.
Generally speaking such a PR would need to contain:
Expose the blob_open() function on SqliteConnection by returning a SqliteBlob type holding a reference to the underlying connection. (Possibly have a read only variant as well). I'm not sure how to handle the row_id lookup there yet. Possibly just expect the user to pass in a primary key value and look up the corresponding row id internally? Maybe even expect a T: IntoUpdateTarget as for update/delete? (Allows using Identifiable or a explicit "query" like users::table.find(42))
The SqliteBlob type needs to implement Drop to call sqlite3_blob_close() if it goes out of scope
The SqliteBlob type needs to implement Write and Read using sqlite3_blob_write and sqlite3_blob_read
We likely want to expose a len() and possibly a is_empty() method based on sqlite3_blob_bytes()
We might want to define zeroblob as sql function somewhere.
Write some tests and documentation.
Overall I think that's a meaningful addition to Diesels API, although I currently do not have the capacity to implement it soon. It still would be great to have that in an feature request, that possibly helps posting the issue to This Week in Rust and similar channels to get someone to try implementing it.
Georg Semmler
npub1xz…j3xh3
2026-02-23 06:53:37 UTC
in reply to nevent1q…d783
Author Public Key
npub1xzxc2qvw9m49pfeqwz94zepycxhzpm6d0nppxcaqpx9r05fd56eq4j3xh3Seen on
wss://relay.mostr.pubPublished at
2026-02-23 06:53:37 UTCEvent JSON
{
"id": "81afec8dd167dd79511c9d62f5460aba5b0c5f001cba3eff72c5c5a4c5a50472",
"pubkey": "308d85018e2eea50a720708b516424c1ae20ef4d7cc21363a0098a37d12da6b2",
"created_at": 1771829617,
"kind": 1,
"tags": [
[
"p",
"ba157608da818c375ad4e95f9858db2838f7fdcad27a03918de592cf28b4e0b5",
"wss://relay.ditto.pub"
],
[
"p",
"9774fa73d93e8079d02b61097a0aae23f9890f35ef99040aec95d0def2f24e27",
"wss://relay.ditto.pub"
],
[
"e",
"379e4bc24e209248605f49abf975aed8d09fc5b4a707132ae2db58cb22968a2d",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://social.weiznich.de/users/weiznich/statuses/116118625836025302",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqhg2hvzx6sxxrwkk5a90eskxm9qu00lw26faq8yvdukfv7295uz6sxwmcwl This is not yet exposed by Diesel, but I would happily merge a PR adding support for it.\n\nGenerally speaking such a PR would need to contain:\n\nExpose the blob_open() function on SqliteConnection by returning a SqliteBlob type holding a reference to the underlying connection. (Possibly have a read only variant as well). I'm not sure how to handle the row_id lookup there yet. Possibly just expect the user to pass in a primary key value and look up the corresponding row id internally? Maybe even expect a T: IntoUpdateTarget as for update/delete? (Allows using Identifiable or a explicit \"query\" like users::table.find(42))\nThe SqliteBlob type needs to implement Drop to call sqlite3_blob_close() if it goes out of scope\nThe SqliteBlob type needs to implement Write and Read using sqlite3_blob_write and sqlite3_blob_read\nWe likely want to expose a len() and possibly a is_empty() method based on sqlite3_blob_bytes()\nWe might want to define zeroblob as sql function somewhere.\nWrite some tests and documentation.\n\nOverall I think that's a meaningful addition to Diesels API, although I currently do not have the capacity to implement it soon. It still would be great to have that in an feature request, that possibly helps posting the issue to This Week in Rust and similar channels to get someone to try implementing it.",
"sig": "be00ddabc800f3b4a5e83005b1cecf8c129ac69d5100e6d38504c2be29226ccf1d411fd73fa9ea9bb27dd1d54a9dcb145c9111cf68420c0905c93e060135128d"
}