Kostadin Bajalcaliev wrote :
>I am using MaxDB 7.5 (_UNICODE = YES, DEFAULT_CODE = UNICODE) and there is a
>very strange situation when i want to create dbproc accepting Unicode
>parameters, a simple procedure as reflection does not work.
>CREATE DBPROC REFL (IN Q VARCHAR(100), OUT R VARCHAR(100)) AS
> R = Q;
>If you call this with anything that is not Ascii (in my case Cyrilic) there
>is an error:
>Auto Commit: Off, SQL Mode: Internal, Isolation Level: Committed
>Restricted data type attributes violation.
>CALL RF ('????',:X)
I don't know who returns this error, in any case it seems not to be an error
returned by the MaxDB server. Can you please tell me from which environment you called
the procedure ?
>How ever when i try to create the procedure as below there is an other
>error.
>CREATE DBPROC REFL (IN Q VARCHAR(100) UNICODE, OUT R VARCHAR(100) UNICODE)
>AS
> R = Q;
>Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed
>Syntax error or access violation;-5015 POS(24) Missing
>keyword:VARCHAR,REAL,NUMERIC,FLOAT,FIXED,DECIMAL,DEC,CHARACTE.
>CREATE DBPROC RF (IN R VARCHAR (100), OUT R VARCHAR(100) UNICODE) AS
> R = Q;
For an unicode instance all [VAR]CHAR parameters of a db-procedure implicitly have the
unicode
property. The explicit specification of UNICODE is not permitted.
Regards,
Thomas
--
Thomas Anhaus
SAP DB, SAP Labs Berlin
[EMAIL PROTECTED]
http://www.sapdb.org/
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
