Subject: Re: [boost] [SQL-Connectivity] Is Boost interested in CppDB?
From: Artyom (artyomtnk_at_[hidden])
Date: 2010-12-14 06:58:13
> >> > 4. Unicode Support in ODBC, i.e. you can use Unicode with MS
> >> > SQL Server that does know speaks in UTF-8, SOCI does not
> >> > support this.
> >>
> >> Right. So how do you support Unicode that's not going through ODBC?
> >
> > Almost every database around fully supports Unicode - sqlite3, postgresql,
> > mysql and many others - they use UTF-8 as the text encoding without
> > any problems.
> >
> > So as long as you keep working with UTF-8 you are on the right way,
> > ODBC backend knows to convert UTF-8 to UTF-16 and backward for thous
> > databases that do not support UTF-8 naively (i.e. MS SQL Server).
> >
>
> Yes, but more specifically I should have asked, does your library
> natively support wide strings (std::wstring) and handle the conversion
> from std::wstring to the appropriate UTF-8 encoding in narrow strings
> API's or the native multi-byte string APIs of the libraries?
No, as you don't need "wide" strings to use Unicode and actually wide
strings are not native ones for almost every database.
So for working with Unicode in CppDB you should use UTF-8.
Artyom