On 22 July 2013 15:29, Pawel Aleksander Fedorynski <pfe...@gmail.com> wrote: > > The problem as I see it is not really with a specific mapping of some > unsigned types to signed types, but with the fact that v.get<...>() throws > when the types don't match exactly, instead of trying to put the value of > the requested field into whatever type the user wants it in (and only > throwing when that's not possible.) The general understanding was that soci > should be changed, I think Mateusz (cc-ed) started writing a design doc > about it.
Generally, I agree with Aleksander. Unfortunately, I haven't managed to move forward with improvements of integer types support, I'm too busy at the moment. My idea was simple to document the C++<->SQL backend mapping first, in order to cover most/all C-language C99 (stdint,h) and C++11 integer types. Then, discuss changes that would be required - ideally if all from/to transformations go through common layer in Core.f Here is table I aimed to fill first: https://github.com/SOCI/soci/wiki/RFC1 Anyone, feel free to start filling this table so we can discuss the exact mappings. FYI, it is planned for SOCI 4.0.0 - no date set. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ soci-users mailing list soci-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-users
