| From: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PL/pgSQL does not accept none ASCII identifiers |
| Date: | 2000-09-13 07:42:54 |
| Message-ID: | 200009130742.CAA01060@jupiter.jw.home |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
> It seems PL/pgSQL accepts only ASCII identifiers. This results in
> column names of Europian or Asian languages are syntax errors for
> example. Fix for this looks simple (see attached patches) but I would
> like to know if there's any intentional reasons for this.
No other reason than that I just forgot about non-ascii
identifiers when I coded that (long long ago). Go ahead and
change it.
Jan
> --
> Tatsuo Ishii
>
> *** scan.l~ Thu May 27 05:55:06 1999
> --- scan.l Thu Sep 7 19:25:36 2000
> ***************
> *** 48,55 ****
> #define YY_INPUT(buf,res,max) plpgsql_input(buf, &res, max)
> %}
>
> ! WS [[:alpha:]_"]
> ! WC [[:alnum:]_"]
>
> %x IN_STRING IN_COMMENT
>
> --- 48,55 ----
> #define YY_INPUT(buf,res,max) plpgsql_input(buf, &res, max)
> %}
>
> ! WS [\200-\377_A-Za-z"]
> ! WC [\200-\377_A-Za-z0-9"]
>
> %x IN_STRING IN_COMMENT
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2000-09-13 07:58:02 | Re: man, I feel like a beginner ... |
| Previous Message | Hannu Krosing | 2000-09-13 06:44:42 | Re: Status of new relation file naming |