New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 901382 link

Starred by 1 user
Status: Assigned
Owner:
treib@chromium.org
Cc:
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Feature

Blocked on:
issue 864519


Sign in to add a comment

PersonalDataManager: Support storing addresses in the account DB

Project Member Reported by treib@chromium.org, Nov 2 
PersonalDataManager is backed by two DBs, the profile DB and the account DB. So far, the account DB supports only credit cards; everything else is always stored in the profile DB.
This bug is about supporting addresses in the account DB. This will likely require some "merge" logic when querying addresses from PDM. Any changes to addresses will have to specify which DB to use.

Comment 1 Deleted

Comment 2 by treib@chromium.org, Nov 8 

Some first notes:
PersonalDataManager already has a concept of "server addresses". So far, these are used only for Wallet billing addresses, are always stored in the profile (i.e. local, persisted) DB, and are immediately copied/merged into the set of local addresses.
Eventually we'll probably have to support two types of "server addresses": The Wallet billing addresses that we have right now, and also regular addresses (AUTOFILL_PROFILE) when in Butter mode.

Comment 3 by se...@chromium.org, Nov 8 

Happy to chat with you if you want more detail on why/how we handle those :)

Comment 4 by treib@chromium.org, Nov 8

Blockedon: 864519
Let's first address bug 864519 (storing the existing "server addresses" aka Wallet billing addresses) in the server DB. Once that's done, we can address storing regular AUTOFILL_PROFILE addresses ephemerally.
►

Sign in to add a comment