From: Dusan Kolesar (d.kolesarcentrum.sk)
Date: Mon Aug 14 2006 - 06:10:36 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, 11 Aug 2006 10:56:18 +0200, Zabach, Elke <elke.zabachsap.com>
wrote:

My database parameters are:
_UNICODE NO
DEFAULT_CODE ASCII

> Dusan Kolesar wrote:
>
>> Hello Elke,
>>
>> It is not working.
>> When I do
>> SET msgAscii = ASCII (msgByte);
>> ---- Error -------------------------------
>> Integrity constraint violation;-8006 POS(6046) Data types must be
>> compatible
>>
>
> Then please send the following info:
> installation parameter
> _UNICODE
> DEFAULTCODE
>
> are those two msg... columns, parameter, variables?
>
> how are they defined?
>
> the combinations I tried do not cause this error, meaning everything
> worked as expected.
> There we have to find out the difference between our experiences
> (despite the version)
>
> The error is found out during creation of the dbproc?
>
> Elke
> SAP Labs Berlin
>
>> Dusan
>>
>> On Thu, 10 Aug 2006 09:46:15 +0200, Zabach, Elke
>> <elke.zabachsap.com>
>> wrote:
>>
>> > Dusan Kolesar wrote:
>> >
>> >>
>> >> Hello,
>> >> I'm using MaxDb 7.6.0.16 on WinXp HE + SP2.
>> >>
>> >> Last time I asked you how to convert Varchar ASCII variabl
>> >> into Varchar
>> >> BYTE
>> >> Your answer was: HEXTORAW (HEX (<char_ascii>)).
>> >>
>> >> Now I need to convert Varchar BYTE variabl into Varchar ASCII
>> >> inside stored procedure.
>> >> Can you advice how to do this ??
>> >>
>> >
>> > Use function ASCII
>> >
>> > BTW: do you think the datatypes in your db are correct if
>> you have to
>> > convert from/to
>> > ascii/byte?
>> >
>> > Elke
>> > SAP Labs Berlin

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]