To circumvent this issue, I have a Multi-Byte wrapper project that does all
the db work. Other projects can be kept as UNICODE.
On Thursday, August 30, 2012, Candy Chiu wrote:
> I'd like to supplement this question with some observation.
>
> When soci-odbc.h is included in an Unicode project, UN
On Thu, 30 Aug 2012 12:38:26 -0400 Candy Chiu wrote:
CC> I have successfully compiled soci and soci-odbc using Visual Studio 2010.
CC> I managed to connect to a DB server and retrieve some data. Everything
CC> worked out well, except I had to change the Character Set property of the
CC> project
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.
Hav
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
