Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cherokee: dev

MySQL authentication, why not do everything in SQL

 

 

Cherokee dev RSS feed   Index | Next | Previous | View Threaded


stefan at konink

Feb 2, 2010, 12:59 PM

Post #1 of 2 (235 views)
Permalink
MySQL authentication, why not do everything in SQL

Hi,


What is the rationale behind not checking the password in SQL directly?

Do you want to skip the SHA or MD5 check if the user is not present?


Stefan
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev


alvaro at octality

Feb 7, 2010, 12:56 PM

Post #2 of 2 (197 views)
Permalink
Re: MySQL authentication, why not do everything in SQL [In reply to]

On 02/02/2010, at 21:59, Stefan de Konink wrote:

> What is the rationale behind not checking the password in SQL directly?
> Do you want to skip the SHA or MD5 check if the user is not present?

It's an interesting idea, indeed!

I suppose that the biggest advantage is a simpler SQL query. It'd be worth implementing a in-SQL check though.

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Cherokee dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.