On Mon, 28 Jan 2013 10:52:44 -0800 Pawel Aleksander Fedorynski
wrote:
PAF> Do you think we should just allow
PAF>
PAF> string s;
PAF> sql << "select 3.14", into(s);
PAF>
PAF> or do you think some new syntax for extra type safety would be warranted,
PAF> e.g.,
PAF>
PAF> string s;
PAF> sql << "
Agreed.
Do you think we should just allow
string s;
sql << "select 3.14", into(s);
or do you think some new syntax for extra type safety would be warranted,
e.g.,
string s;
sql << "select 3.14", into_string(s);
?
Thanks,
Aleksander
On Mon, Jan 28, 2013 at 9:14 AM, Vadim Zeitlin wrote:
>
On Mon, 28 Jan 2013 08:58:05 -0800 Pawel Aleksander Fedorynski
wrote:
PAF> So am I getting this right: what you essentially need is the ability to
PAF> override the field type provided by the database engine (double in this
PAF> case) with one provided by the user (which would be probably string
Hello!
Up to this day I knew every soci bug could be fixed.
But now I don't see any appropriate way to patch soci.
Example is attached.
I cannot modify sql query. Because it is passed from a plugin.
query: "select round( -00237735.42999, 2 )";
Expected value: -00237735.43
tcpdump shows
