RE: SQLDBC: Can't get error message from DBPROC if it contains cyrillic

Tue, 22 Nov 2005 00:36:28 -0800 

Hello Alexey,

the problem with Unicode characters in the error text is known
(http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1138788)

and fixed in 7.6.00.19 (which is not yet available, unfortunately).

Regards
Alexander Schröder
SAP DB, SAP Labs Berlin 

-----Original Message-----
From: Alexey Gaidukov [mailto:[EMAIL PROTECTED] 
Sent: Dienstag, 22. November 2005 09:03
To: maxdb@lists.mysql.com
Subject: SQLDBC: Can't get error message from DBPROC if it contains cyrillic

MaxDB 7.6.00.16

CREATE DBPROC test AS
BEGIN
    STOP(-20020, '123 some cyrillic here 456');
END;


SQLDBC 7.6.00.16


SQLDBC_PreparedStatement_prepareNTS(imp_sth->m_prepstmt, 
statement,SQLDBC_StringEncodingType_Encoding_UTF8;
  exec_rc = SQLDBC_PreparedStatement_executeASCII(imp_sth->m_prepstmt);
  if ( exec_rc != SQLDBC_OK && exec_rc != SQLDBC_NO_DATA_FOUND) {
    SQLDBC_ErrorHndl *errhdl = 
SQLDBC_PreparedStatement_getError(imp_sth->m_prepstmt);
    char* errmsg = SQLDBC_ErrorHndl_getErrorText(errhdl)
    printf("%d '%s'\n", strlen(errmsg),errmsg);
  }



Following SQLDBC documentation SQLDBC_ErrorHndl_getErrorText returns 
UTF8 string. But I get


11 'POS(0) 123 '


-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to