Den Thu, 30 May 2013 13:37:13 +0200 skrev Mateusz Loskot <[email protected]>: > > Brian, > > Thanks for reporting this. > > No, you are not missing anything, your use case looks fine. > > It seems there is a bug in SOCI caused by uninitialised indicator members > of conversion_into_type and conversion_use_type specialisations. > > I have opened issue: > > https://github.com/SOCI/soci/issues/152 > > and I have proposed fix in this pull request > > https://github.com/SOCI/soci/pull/153 > > It hasn't been merged, as it is to be decided if we want to > postpone release of this fix until SOCI 4.0.0. > > Meanwhile, if you could check if this fix solves your problem, > that would be very helpful. You can grab it from my fork of the repo > and checkout bugfix/152-indicators branch: > > git clone git://github.com/mloskot/soci.git > git checkout bugfix/152-indicators > > then build SOCI and test your program with it. > > Best regards,
Yep, that seems to work nicely! Thanks a lot! :-) /Brian ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
