From: Dennis Luehring (dl.soluz_at_[hidden])
Date: 2024-11-19 10:58:42
Am 19.11.2024 um 11:51 schrieb Dominique Devienne via Boost:
> 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.
i would prefer a default check-for-null behavior but the possiblity to
ommit the checks if wanted