diff options
author | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-17 22:37:51 +0000 |
---|---|---|
committer | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-17 22:37:51 +0000 |
commit | 568a8c740e26c089b19f3b11da0648e551bef2f5 (patch) | |
tree | b0d9f74546b56b7513cda67d2c923e87ec0df701 /base/nss_init.cc | |
parent | 23fa003f2eefd24ca32ba82421c86e59bd82810f (diff) | |
download | chromium_src-568a8c740e26c089b19f3b11da0648e551bef2f5.zip chromium_src-568a8c740e26c089b19f3b11da0648e551bef2f5.tar.gz chromium_src-568a8c740e26c089b19f3b11da0648e551bef2f5.tar.bz2 |
Remove per-field dirty bits from EntryKernel.
Always write complete rows into the database. Unify the Update/Create paths by using INSERT OR REPLACE. Remove the IS_NEW field.
Expand one unit test to be sure they exercise the dirty-clearing behavior of SaveChanges.
This is done in preparation for moving to protobuf-based storage. When most fields are merged into a single protobuf column, tracking dirtiness on a per-field basis doesn't buy much.
BUG=30041
TEST=existing unit tests
Review URL: http://codereview.chromium.org/507029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34886 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/nss_init.cc')
0 files changed, 0 insertions, 0 deletions