st.got_data() simply returns the current member and doesn't any action.
If your request expects only 1 record returned back, than you are at this
secanios:
1.) only st.got_data() -> false because nothing executed so far
2.) st.fetch(); st.got_data() -> false too because fetch() returned true fo
layer for now).
regards
Heiko
> "[email protected]" hat am 25. Juni 2013
> um 17:58 geschrieben:
>
> Beside the implementation of MSSQL unicode support over std::string I
> stumbled over the unsupported BLOB capabilities of SOCI in terms of ODBC.
> We
Beside the implementation of MSSQL unicode support over std::string I stumbled
over the unsupported BLOB capabilities of SOCI in terms of ODBC.
We would use SOCI as replacement ina 3.2M codelines middleware project but we
have to check carefully all capabilities upfront.
SOCI is still within the sc
Hi Sergey,
I'm interested into the modified version, you can send me a zip file if you
want.
In meantime i have done a complete implementation of a second string type
(std::wstring) beside the existing std::string type.
If have tested it with vectors, use/into and also with row and rowset support
I need to support MSSQL Server with proper Microsoft UNICODE usage (nvarchar
column etc.) from UCS2 to UTF8 and reverse,
cause MSSQL Server is the only one database engine, the is still not able to
store/retreive UTF8 (even if the actual server is 2012)!
My plan is to clone the ODBC backend and com
