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 SAA11122 for ; Fri, 26 Nov 1999 18:35:16 -0500 (EST) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-sql@hub.org id m11rUkz-0003kJC; Sat, 27 Nov 99 00:26 MET Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: [SQL] national character once again To: kkokoszk@ite.waw.pl Date: Sat, 27 Nov 1999 00:26:25 +0100 (MET) Cc: pgsql-sql@hub.org Reply-To: wieck@debis.com (Jan Wieck) In-Reply-To: <199911261552.HAA31022@www.geocrawler.com> from "Artur Kokoszka" at Nov 26, 99 07:52:15 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > This message was sent from Geocrawler.com by "Artur Kokoszka" > Be sure to reply to that address. > > Two weeks ago I asked about plpgsql errors > (message titled "national characters in plpgsql") > and I didn't get any answer. I can't find the > anwer myself, so please write me something about > this (if it's too simple - I'm sorry, if nobody > knows the answer - please write whotever, I will > know, that somebody read it) > Thank you for understanding. > Artur. PL/pgSQL has it's own language parser, and that one doesn't recognize characters like ³ as valid for attribute or variable names. Nor is it capable of case sensitive names inside of double quotes up to now - still something to do. 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) #