> On Thu, 09 Mar 2000, Dave Kitabjian wrote:
> > Thank you both for your replies.
> >
> > RewriteUsername would work fine except for one major problem: I don't know
> > the case of the username as stored in the database. Names are entered
> > automatically by customer request software (ie, the CD our ISP ships out).
> >
> > Regarding that it would be "impossible", I'm not convinced of that yet. I'm
> > not sure how the various AuthBy algorithms work, but in SQL, for example,
> > you'd simply do:
> >
> > SELECT username
> > FROM Accounts
> > WHERE LOWER(username) = LOWER(User-Name)
> >
> > In otherwords, compare the lower (or upper) case variety of each for
> > matches. That is the functionality that I'm seeking. Otherwise, I'm going
> > to have to clean all our existing data, and then implement some code to
> > intercept all db entries and convert them to lower case. I was hoping to
> > avoid that mess.
> >
>
> What are you using for a database currently? If it is SQL, then why can't you
> just do what you describe above with an AuthSelect? Alternatively, use a stored
> procedure on the backend.
We're using CDB (for maximum speed and huge username count). That's why SQL tricks are
not an option :(
Dave
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
