On Sat, Sep 6, 2025 at 11:57 PM Mohammad Nejati via Boost < boost@lists.boost.org> wrote:
On Fri, Sep 5, 2025 at 11:55 PM Andrzej Krzemienski via Boost <boost@lists.boost.org> wrote:
Unless it is possible in those cases to pass a pointer to `connection` object from sqlite to user code, the next best option, as I see it,
would
be to have a connection_view` class, much like we have `string` and `string_view`.
Klemens, since this has been brought up regularly, what do you think about introducing a connection_ref type that is explicitly non-owning? The use cases for a non-owning connection seem limited to modules and sqlite::context<...>::get_connection(). Passing an instance of a connection_ref seems reasonable.
While I think having a single type is easier, the regularity does show that I hold a minority position. It seems to be rather confusing and worrying to almost everyone else. I'll add a `connection_ref` type that is implicitly constructible from a `connection` and explicitly from a `sqlite3` pointer and make the connection always owning.
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/7TCMMZV3...