On Sun, 23 Jun 2013 13:03:32 +0200 (CEST) "heiko.r...@code-styling.de" <heiko.r...@code-styling.de> wrote:
hs> My plan is to clone the ODBC backend and come up with a first version hs> of a new MSSQL interface. Hello, Having a native MS SQL backend would be very nice to have in any case, even independently of the Unicode issues, so it would be definitely great to at least start working on this. hs> But there is a global issue doing so. I need the extends the core with hs> support of hs> hs> #define SQL_WCHAR (-8) hs> #define SQL_WVARCHAR (-9) hs> hs> with a new core data_type hs> hs> dt_wstring hs> hs> and exchanged to hs> hs> std::wstring. This would be already useful and AFAICS shouldn't be a big problem to implement but I think it would be really useful to also allow exchange between Unicode database fields and UTF-8-encoded std::string (no "w"). What do you think? hs> Should the support additionally enrolled to any other backend too if hs> the backend is able to support such types using std::wstring? Ideally all this should be backend-independent, of course. Even if the backend doesn't specifically support Unicode at all, we could just encode std::wstring in UTF-8 and use the existing code. In fact, I'd think that this would be the right thing to do for all the other backends but I didn't actually check it. Regards, VZ
pgpAWGd_pzPFX.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ soci-users mailing list soci-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/soci-users
