SEE ATTACHMENT
acip.vcf (298 Bytes)
acip.vcf (328 Bytes)
Aci,
CREATE OR REPLACE PROCEDURE aaa_test IS
char4 VARCHAR2(4 CHAR) := 'abcč';
BEGIN
Null;
END;
You are using "4 CHAR" sets so the initialisation should be ok,
however, it is possible that you might need NVARCHAR2(4 CHAR) if your
database character set is single byte.
The last character in your string above is most likely multi-byte and
VARCHAR uses the database character set so may only allow 4 bytes (bytes
= characters in a single byte character set).
Compiling or formatting my source code gives me an error message
'[Error] Syntax check (2: 10): ERROR line 2, col 10, ending_line 2,
ending_col 25: The string initializer has a value which is too long':
Leads me to suspect that your database character set is indeed single byte!
If I change my definition of char4 variable from varchar2(4) to
varchar2(5) then it is OK.
Yes, until you come across a string with more than one character that
requires more than one byte!
What is the reason for this as SQL*Plus compiles OK in both cases.
Hmmm. Interesting!
I wonder if your Oracle client is to blame? Toad is unicode from 10
onwards and a 9i client doesn't cut it with unicode. You need a 10g client.
--
Cheers,
Norm. [TeamT]
SEE ATTACHMENT
SEE ATTACHMENT
SEE ATTACHMENT
acip.vcf (328 Bytes)
SEE ATTACHMENT
SEE ATTACHMENT
SEE ATTACHMENT
that’s an impressive email signature.
that’s an impressive email signature.
that’s an impressive email signature.
that’s an impressive email signature.
that’s an impressive email signature.