diff options
| author | pkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-29 18:24:01 +0000 |
|---|---|---|
| committer | pkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2008-10-29 18:24:01 +0000 |
| commit | ab184cc284a629e1139363257d1b9082b4cb2e33 (patch) | |
| tree | 384f681e12898a3c2ff7c3c7e38aa9ba57583d63 /gears | |
| parent | 70f45c3f2b52eb71f15e707c9f21ff98c221758e (diff) | |
| download | chromium_src-ab184cc284a629e1139363257d1b9082b4cb2e33.zip chromium_src-ab184cc284a629e1139363257d1b9082b4cb2e33.tar.gz chromium_src-ab184cc284a629e1139363257d1b9082b4cb2e33.tar.bz2 | |
Trivial patch: add whitespace to some SQL statements to turn "INSERT INTO foo(bar,baz)VALUES(?,?)" into "INSERT INTO foo (bar, baz) VALUES (?,?)" (which is the way we have it in most of our code).
This was annoying me while I tried to track down cases where we omitted the appropriate fieldnames from our SQL statements.
Review URL: http://codereview.chromium.org/8855
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4145 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gears')
0 files changed, 0 insertions, 0 deletions