summaryrefslogtreecommitdiffstats
path: root/net/http/http_network_transaction.h
diff options
context:
space:
mode:
authorpkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2008-10-29 17:09:15 +0000
committerpkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2008-10-29 17:09:15 +0000
commitf1775c74f4cb83320ca53b82dc4e3c28c754d6d9 (patch)
treebefd62a2951f52e9b47ac1f224c8a15a2ab62865 /net/http/http_network_transaction.h
parent2da95da3c557c70318900db9a9e06876dedf3e94 (diff)
downloadchromium_src-f1775c74f4cb83320ca53b82dc4e3c28c754d6d9.zip
chromium_src-f1775c74f4cb83320ca53b82dc4e3c28c754d6d9.tar.gz
chromium_src-f1775c74f4cb83320ca53b82dc4e3c28c754d6d9.tar.bz2
Add fieldnames to SQL statements for better forward-compatibility. Had we had this code in place already, I wouldn't have needed to rev the compatible version number in my upcoming database change >:(
I checked the rest of our sourcebase's INSERT and SELECT statements, but these were the only ones that needed to have fieldnames added (in a few cases SELECT * was appropriate). Review URL: http://codereview.chromium.org/8684 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4130 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/http/http_network_transaction.h')
0 files changed, 0 insertions, 0 deletions