This is getting somewhat ridiculous but it looks that wherever I look at ODBC backend code I find a problem. The latest one is in its odbc_standard_use_type_backend::post_use(): what is the point of overwriting the *input* parameters with the values we have provided for ODBC driver ourselves? This doesn't seem to make any sense, this data is never modified by ODBC to the best of my knowledge (again, we're speaking about SQL_PARAM_INPUT here), so why should we do this? Does anybody know of any problems that would happen if post_use() part dealing with data is simply removed?
I realize that it's probably high time to stop asking questions and just forget about using ODBC with SOCI completely but perhaps somebody knows the answer to this one? Thanks, VZ
pgpJddSBuGW08.pgp
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Soci-users mailing list Soci-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-users
