Confusing behavior for statement::bind with character types

[anarthal]

This is correct:

stmt.bind(uint8_t(42)); // understood as an integer

But this is confusing and should probably not be allowed:

stmt.bind('a'); // understood as an integer too, 97

Applies to char, wchar_t, and charN_t