Message-ID: <937d27e10806110826r5afbf33aoc0daa12e59b63171@mail.gmail.com>
Date: Wed, 11 Jun 2008 16:26:39 +0100
From: "Dave Page" <dpage@pgadmin.org>
To: "Greg Sabino Mullane" <greg@turnstep.com>
Subject: Re: New software catalog fails (why are we spelling it "catalogue"?)
Cc: pgsql-www@postgresql.org
In-Reply-To: <937d27e10806110753m4990ecfbl7cd686ec9036640b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <34153382302f195bf55fa71338367f0c@biglumber.com>
	<937d27e10806110753m4990ecfbl7cd686ec9036640b@mail.gmail.com>

On Wed, Jun 11, 2008 at 3:53 PM, Dave Page <dpage@pgadmin.org> wrote:
> Rats. That happens because *%*=A3$% MediaWiki insists on re-casing names
> so we had to make the logon code case-insensitive. You need to logon
> using the same casing as we have stored in the database to satisfy the
> foreign key. Meanwhile, I'll be fixing up the code to try to handle
> that....

For the benefit of those interested in this sort of thing, I've fixed
this by having community_logon() return the userid as found in the
database rather than as the user entered, so subsequent code finds it
with the correct casing. The userid parameter was already declared
INOUT so 'twas a simple change.


--=20
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com