Re: [boost] SQL: next iteration of sqlpp11

Subject: Re: [boost] SQL: next iteration of sqlpp11
From: Klaim - Joël Lamotte (mjklaim_at_[hidden])
Date: 2014-02-03 11:56:14

On Mon, Feb 3, 2014 at 5:33 PM, Edward Diener <eldiener_at_[hidden]>wrote:

> In most usecases I encountered so far, it is totally OK to interpret
>> NULL values like default values, e.g. NULL strings and empty strings, or
>> NULL foreign keys or 0LL. For those usecases it would be quite annoying
>> to have to check if there really is a value, or always use
>> get_optional_value_or...
>>
>
> You are wrong ! Having a database NULL value is completely different from
> having an empty string or a 0 value. Please reconsider. The boost::optional
> is the correct choice.

+1