From: Peter J. <pj...@wa...> - 2004-02-26 21:28:59
|
Hi Alessandro, All, "Alessandro Petrelli" <pet...@in...> wrote: > I have an unicode_fss db (I need to develop a Japanese application) and = an > asp.net DataGrid. All fields are shown correctly except those for which = I > call declarative databinding, for example: [...] > The field OUT_CHANNEL is return from a stored procedure and is a char(1)= . I > should expect values like 'P' or 'E', but instead they are returned as '= P ' > or 'E '. The sad fact is, that this field will also happily hold 'PPP' and 'EEE' or= 'P=D6' but not '=D6=D6', if you see what is going on here. (Perhaps the NE= T provider actually manages to forbid these INSERTs, but with the C API or ISQL it's possible.) Now, at SELECT time, a clever middle layer (like the NET provider ;-) ), can try to make the situation more sane. Knowing that a 3 byte buffer for UNICODE_FSS should better only hold one character, it can algorithmically extract just one UTF-8 character from the buffer, ignoring the junk bytes after that. Regards, Peter Jacobi |