Autofill database migration to clean up bogus profiles.

chrome/browser/autofill/autofill_profile.cc

Index: chrome/browser/autofill/autofill_profile.cc
diff --git a/chrome/browser/autofill/autofill_profile.cc b/chrome/browser/autofill/autofill_profile.cc
index 5aa474a0de8ff4d187c242ebe0379ea4a20300d7..b7a3e984222fca64822fcefd51e6021430e85dd2 100644
--- a/chrome/browser/autofill/autofill_profile.cc
+++ b/chrome/browser/autofill/autofill_profile.cc
@@ -311,8 +311,7 @@ bool AutofillProfile::operator!=(const AutofillProfile& profile) const {
 const string16 AutofillProfile::PrimaryValue() const {
   return GetFieldText(AutofillType(NAME_FULL)) +
          GetFieldText(AutofillType(ADDRESS_HOME_LINE1)) +
-         GetFieldText(AutofillType(ADDRESS_HOME_LINE2)) +
-         GetFieldText(AutofillType(EMAIL_ADDRESS));

[Ilya Sherman, 2011/03/16 23:07:16]

This isn't the right fix for not merging with empty emails.  For one, the same
problem exists with empty names.  Moreover, we added the email address to the
"primary value" because we got a lot of pushback when we started automatically
merging email addresses --
http://code.google.com/p/chromium/issues/detail?id=64669

I think it would be better to address this in a separate cl, for clarity's sake.
 However, if we want to cover this case in the migration that *this* CL
implements, then we should make sure to commit the other CL first.  I think it's
actually ok to just not worry about it for now -- we're going to do another
migration later, so it should be fine to handle edge cases like this one at that
time.

[dhollowa, 2011/03/17 00:02:42]

Yes, true.  Will address later.

On 2011/03/16 23:07:16, Ilya Sherman wrote:

+         GetFieldText(AutofillType(ADDRESS_HOME_LINE2));
 }
 
 string16 AutofillProfile::ConstructInferredLabel(