scripts/sqlite2cpp.py requires insert of nullable column about sqlpp11 HOT 6 CLOSED

Hi,

What result line should be?

using _traits = sqlpp::make_traits<sqlpp::integer, sqlpp::tag::require_insert>;
or
using _traits = sqlpp::make_traits<sqlpp::integer, sqlpp::tag::can_be_null>;
or both
using _traits = sqlpp::make_traits<sqlpp::integer, sqlpp::tag::can_be_null, sqlpp::tag::require_insert>;
?

My current generator gives 2nd line.

from sqlpp11.

using _traits = sqlpp::make_traits<sqlpp::integer, sqlpp::tag::can_be_null>;

This is correct (result of the linked commit, b92a9a7). I was wondering if there are versions of sqlite3 that return a string for the notnull column (that was the previous behavior). If unclear, then we should keep it this way.

from sqlpp11.

What can return column[3] == 0 here?

sqlCanBeNull = column[3] == 0 or column[3] == '0'

from sqlpp11.

The old code used column[3] == '0'. That did not work correctly on my machine since column[3] a numeric value.

That's why the new code uses column[3] == 0 in addition.

My question is: Are there versions of sqlite3 that yield a string in column[3]?

from sqlpp11.

I had always "0" in my code.
https://github.com/egorpugin/primitives/blob/master/src/tools/sqlpp11.sqlite2cpp.cpp#L222
Sqlite returns char * value 0 or 1, so I compare it with "0";

from sqlpp11.

Interesting. In python the result is numeric. At least on my machine.

Thanks for looking into it. I'll leave as is.

from sqlpp11.