I'd like to supplement this question with some observation.
When soci-odbc.h is included in an Unicode project, UNICODE is turned on,
causing the API functions to be remapped to their W (wide character)
siblings. Since std::string is hardcoded in the declaration, the code no
longer compiles.
Have anyone encountered a similar issue?
On Thursday, August 30, 2012, Candy Chiu wrote:
> Hi,
>
> I have successfully compiled soci and soci-odbc using Visual Studio 2010.
> I managed to connect to a DB server and retrieve some data. Everything
> worked out well, except I had to change the Character Set property of the
> project from "Use Unicode Character Set" to "Use Multi-Byte Character Set"
> to get the code compiled. Since I don't have much experience with the
> character sets, I am a little leery of changing the default value. Would
> someone provide some insights into why the Multi-Byte Character Set is
> required? If it is something easy to fix, I am glad to do it.
>
> Thanks,
> Candy
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
