MySQL Bugs: #3819: Can 'Access Control Phase 1' (manual 5.4.5) be made to check the host table?

Bug #3819	Can 'Access Control Phase 1' (manual 5.4.5) be made to check the host table?
Submitted:	18 May 2004 19:49
Reporter:	Brian Nelson	Email Updates:
Status:	Open	Impact on me:	None
Category:	MySQL Server: Security: Privileges	Severity:	S4 (Feature request)
Version:	4.0.20	OS:	Solaris (Solaris 9)
Assigned to:		CPU Architecture:	Any

Description:
(from manual)
A blank Host value in a db table record means that its privileges should be combined with those in the entry in the host table that matches the client hostname. The privileges are combined using an AND (intersection) operation, not OR (union). 
---

Can this behaviour be made to also occur for a blank Host value in the user table?

The problem is that I have many users who need to be able to connect from both localhost and %.mydomain.com. The only way to do this is to maintain two user entries for each account. This is not only a major administrative headache. It is also confusing to the user, as changing their password will only effect one of the user table entries (depending on where they are connected from).

It would be very bennificial to be able to make the 'phase 1' check against the host table to determine allowing access.

How to repeat:
none needed

Suggested fix:
Make 'blank Host value in user table' behave the same way as 'blank Host value in db table' does.