On 23 June 2013 12:03, [email protected] <[email protected]> wrote: > 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 come up with a first version of a > new MSSQL interface. > Later on i would modifiy it to use the native client capabilities for better > performance.
I forgot to address the use of native client, I think it's a very good idea, it's been around for a while: https://github.com/SOCI/soci/wiki/Roadmap Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
