Re: [patch] Auth to have case sensitive username matching in DB container
| From: | Ian Eure | Date: | Thu, 13 May 2004 05:43:14 +0000 |
| Subject: | Re: [patch] Auth to have case sensitive username matching in DB container | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-29171@lists.php.net to get a copy of this message | ||
On Wednesday 12 May 2004 04:04 pm, Yavor Shahpasov wrote:
> I have not understood what this patch is trying to do.
>
> do you mean that 'Joe' != 'joe' where joe/Joe is the username or have i
> completly missed the point.
> what is your target database.
>
It appears that for some (broken?) databases, doing a SELECT WHERE usernamecol
= 'jOe' will match a row where usernamecol = 'joe'. The submitter doesn't
specify what database they are using, but this certainly seems like incorrect
behavior. I know that PostgreSQL won't do this, and MySQL only does
case-insensitive searches if you use LIKE.
The patch verifies that the username returned from the database matches the
requested username exactly.
Seems like a database bug to me, and not a BC break to make sure that 'jOe' =
'JOe' and not 'joE'.