From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | phede-ml(at)islande(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unicode combining characters |
Date: | 2001-09-26 12:43:22 |
Message-ID: | 3BB1CD6A.3DA8D7E1@fourpalms.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> BTW, I see "CHARACTER SET" in gram.y. Does current already support
> that syntax?
Yes and no. gram.y knows about CHARACTER SET, but only for the long
form, the clause is in the wrong position (it preceeds the length
specification) and it does not do much useful (generates a data type
based on the character set name which does not get recognized farther
back). Examples:
thomas=# create table t1 (c varchar(20) character set sql_ascii);
ERROR: parser: parse error at or near "character"
thomas=# create table t1 (c character varying character set sql_ascii
(20));
ERROR: Unable to locate type name 'varsql_ascii' in catalog
I'm pretty sure I'll get shift/reduce troubles when trying to move that
clause to *after* the length specifier. I'll try to do something with
the syntax for 7.2 once I've finished the date/time stuff.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Reinoud van Leeuwen | 2001-09-26 12:53:14 | optimizer question |
Previous Message | Jan Wieck | 2001-09-26 12:10:08 | Re: tuple statistics function |