Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id KAA35485 for ; Wed, 5 Jan 2000 10:10:39 -0500 (EST) (envelope-from wieck@debis.com) Received: from debis.com by orion.SAPserv.Hamburg.dsh.de with smtp for id m125rsq-0003kGC; Wed, 5 Jan 100 15:57 MET Sender: wieck Message-ID: <38735DBB.360E369B@debis.com> Date: Wed, 05 Jan 2000 16:05:31 +0100 From: Jan Wieck X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Kovacs Zoltan CC: pgsql-sql@postgreSQL.org Subject: Re: [SQL] plpgsql bug(?) References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Kovacs Zoltan wrote: > Dear Jan, > > The problem occurs with "vevõ = new.az", I think the plpgsql parser > stops processing the field name "vevõ" because "õ" (code 245) > is not a standard ASCII character, it is from the Latin2 set. > I tried other non-international characters like "é" (code 233) > without success. > > Could you please help, where to modify the sources to make this work? > I am using version 6.5.2. Unfortunately I cannot reproduce that behaviour here. Seems that your version of lex(1) has another understanding of the character class [:alnum:] than my one. I can use äöü (a-diaeresis etc.), µ (greek my character) and ³ (3 superscripted) too. I'm using flex-2.5.4 here. But I'm not really sure it is that itself, maybe flex is using isalnum() from the standard C library inside. Then it would be more tricky. You can play around with the two character sets WS and WC declared at the top of src/pl/plpgsql/src/scan.l They are slightly extended regular expressions (the class notation inside). Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #