Re: [review] [sqlite]

From: Ruben Perez (rubenperez038_at_[hidden])
Date: 2024-11-19 09:05:19

On Tue, 19 Nov 2024 at 09:37, Klemens Morgenstern
<klemensdavidmorgenstern_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.
>
>
> sqltie:;value would work. I should add optional support though.

It doesn't seem to work. Apparently, some part of the machinery
requires the row type to be default-constructible, making
sqlite::value unusable in that context.

Anyway, sqlite::field explicitly states it's for query results, while
sqlite::value is for usage in internal APIs. This is holding the
results of a query, so why is it sqlite::value the one that looks to
be supported?