On Fri, Sep 12, 2025 at 3:57 PM Vinnie Falco <vinnie.falco@gmail.com> wrote:
- connection ownership ambiguity: - resultset ownership ambiguity:
I'd be curious to see how other libraries solve this problem, if at all.
Klemens could probably answer this question better, but from my research, sqlite_orm (a C++ library) has a connection_ref (which seems to be used only internally), while the others libs have only a single owning connection type. rusqlite, (a Rust library) uses the same owning/non-owning model as the proposed Boost.Sqlite, but connection::from_handle is marked unsafe, even though I do not think it helps the user reason about ownership. Regarding the resultset issue, the functionality is usually implemented in the statement class because there is no standalone resultset object in SQLite and it always needs to refer to a statement.