This may be useful in the database domain, but I don't think it applied to most web contexts.
Most web applications don't bother with database security - it muddles the logic and prevents things like pooling, scale, etc
For more traditional web apps - typically you have two sources accessing the database - the Web Application and the Administrators. Both of which have access to nearly everything anyway.
This might stop some malicious code from accessing the database improperly - but the fact is, if someone can manipulate the code you've already lost anyway (they could simply just capture the passwords at entry for example).
Comments
This may be useful in the database domain, but I don't think it applied to most web contexts.
Most web applications don't bother with database security - it muddles the logic and prevents things like pooling, scale, etc
For more traditional web apps - typically you have two sources accessing the database - the Web Application and the Administrators. Both of which have access to nearly everything anyway.
This might stop some malicious code from accessing the database improperly - but the fact is, if someone can manipulate the code you've already lost anyway (they could simply just capture the passwords at entry for example).