Re: [review] [sqlite]

From: Dominique Devienne (ddevienne_at_[hidden])
Date: 2024-11-19 10:51:49

On Tue, Nov 19, 2024 at 9:37 AM Klemens Morgenstern via Boost
<boost_at_[hidden]> wrote:
> On Tue, Nov 19, 2024 at 4:30 PM Ruben Perez <rubenperez038_at_[hidden]> wrote:
> > What's the best way to specify a nullable field in the static
> > interface? std::optional<T> and boost::optional<T> don't seem to work,
> > nor does having a sqlite::field member.
> sqlite::value would work. I should add optional support though.

I use optional extensively in my SQLite and PostgreSQL wrappers.
And on result-sets, trying to read / access a NULL into a non-optional
value throws. I.e. the client must expect the NULL and code accordingly.

Not sure what the current situation is given Ruben's question,
but support for optional is important to my use cases at least, FWIW. --DD