On 26 June 2013 00:37, Mateusz Loskot wrote:
> On 24 June 2013 17:14, Vadim Zeitlin wrote:
>
>> So my suggestion would be:
>>
>> 1. Handle only UTF-8 for multibyte encodings right now and, perhaps, throw
>>an error if we can detect that the database uses anything else.
>>Formalize this b
On 24 June 2013 17:14, Vadim Zeitlin wrote:
> On Mon, 24 Jun 2013 16:47:32 +0100 Mateusz Loskot wrote:
>
> ML> Do you mean a field of UTF-8 and select into(std::wstring)
> ML> or field of UTF-16 and insert with use(std::string) ?
>
> Both. I.e. IMO ideally any text database fields, be they UTF-8
Hi, Heiko
Yes, I can understand, that conversion can be a problem, but std::widestring is
a
broblem itself, actually.
Only on windows it represents UCS2, but on all other platforms it is UCS32!
So both ways are error-prone. Question is how to choose between two evils.
I prefer utf8 based impl
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
On Mon, 24 Jun 2013 16:47:32 +0100 Mateusz Loskot wrote:
ML> > hs> But there is a global issue doing so. I need the extends the core with
ML> > hs> support of
ML> > hs>
ML> > hs> #define SQL_WCHAR (-8)
ML> > hs> #define SQL_WVARCHAR (-9)
ML> > hs>
ML> > hs> with a new core dat
On 24 June 2013 14:50, Sergey Stepanov wrote:
>
> If you really interested, I have fully working version of the ODBC backend
> with Unicode fields implemented.
> I can share the code, but it would be really cool if someone will help me
> pushing those changes to SOCI repository.
> In my implemen
On 24 June 2013 14:36, Vadim Zeitlin wrote:
> On Sun, 23 Jun 2013 13:03:32 +0200 (CEST) "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 ver
Hi, Everyone
If you really interested, I have fully working version of the ODBC backend with
Unicode fields implemented.
I can share the code, but it would be really cool if someone will help me
pushing those changes to SOCI repository.
In my implementation I used UTF8 based columns support wit
On Sun, 23 Jun 2013 13:03:32 +0200 (CEST) "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 Unicod
On 23 June 2013 12:03, heiko.r...@code-styling.de
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 ac
On 23 June 2013 12:03, heiko.r...@code-styling.de
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 ac
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
12 matches
Mail list logo
