Message-ID: <4807823B.40706@postnewspapers.com.au>
Date: Fri, 18 Apr 2008 01:00:43 +0800
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
Cc: pgsql-performance@postgresql.org
Subject: Re: SQL Function Slowness, 8.3.0
References: <af1bce590804160806t58f7da1g50fc697dd9e6ab08@mail.gmail.com>	
	<8328.1208358587@sss.pgh.pa.us>
	<1208448751.4259.317.camel@ebony.site>	
	<20970.1208448770@sss.pgh.pa.us>
	<1208449557.4259.331.camel@ebony.site>
In-Reply-To: <1208449557.4259.331.camel@ebony.site>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Simon Riggs wrote:

> Obfuscating the names would make the code harder to understand, true,
> but only if the code is written in English (or your language-of-choice).
> It wouldn't damage our ability to read other language code at all.

Speaking of this sort of support tool, what I personally often wish for 
is unique error message identifiers that can be looked up (say, with a 
web form) or a way to un/re-translate localized messages.

I'm on one other mailing list where a wide variety of languages is in 
use; however, on that list there are lots of experienced users - 
including most of the translators for the app - happy to help out in the 
users preferred language or to translate. Here much of the help seems to 
be from mostly English (only?) speakers, so a reverse message translator 
back to the English used in the sources would be pretty cool.

I should have a play and see how hard it is to generate a reverse 
translation tool from the .po files.

I do think that something that could substitute replacement generic 
variable names consistently throughout a schema, set of queries, EXPLAIN 
/ EXPLAIN ANALYZE output, etc would be handy, though it'd be better if 
people just posted their original code.

--
Craig Ringer