summaryrefslogtreecommitdiffstats
path: root/chrome/browser/meta_table_helper.cc
Commit message (Collapse)AuthorAgeFilesLines
* Fix gcc warning about possible unused variable experienced with Apple gcc 4.2mark@chromium.org2009-08-201-2/+2
| | | | | | | in an -O3 experiment. Review URL: http://codereview.chromium.org/173124 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23860 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor MetaTableHelper to remove redundant table name prefixing with databaseyuzo@chromium.org2009-07-021-17/+35
| | | | | | | | | | | | name. Also, PrimeCache logic duplicated in HistoryBackend and SQLitePersistentCookieStore is moved to this class. BUG=none TEST=n/a Review URL: http://codereview.chromium.org/150094 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19802 0039d316-1c4b-4281-b951-d872f2087c98
* Correct sqlite wrapper behavior on systems where wchar_t is UTF-32,phajdan.jr@chromium.org2009-01-301-2/+2
| | | | | | | | | | | | for example Linux. The problem was that old code assumed wstring is UTF-16, which resulted in string corruption on Linux. I actually tested it on browser/history unit tests, see http://codereview.chromium.org/18758. Review URL: http://codereview.chromium.org/18805 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8977 0039d316-1c4b-4281-b951-d872f2087c98
* Add compatible version support since it was only halfway in place, and try ↵pkasting@chromium.org2008-10-301-1/+2
| | | | | | | | | | | | | and make our database versioning code and logging more similar across various consumers. The compatible version support isn't really used yet. It was going to be used for my cookie change until we decided that the old code was too busted to be forward-compatible. It seems worthwhile to put this in but maybe I am wrong. The logging similarity stuff is fairly useful. In a couple consumers in the old code, we DLOGed instead of LOGing, which meant that most people would get nothing in the log at all. I think it's a little weird that in a lot of these consumers, logging is all we do; for example, if you use a too-new cookie DB, you get output in the log, but no actual dialog box while the browser is running -- your cookies just silently don't get saved to disk. Seems bad, but I'm not prepared to try and do major surgery to address that (and add translated strings, etc.). At least now we'll actually get log messages in release builds instead of nothing at all. Because my last-access change touches this code, I'm considering asking that this change be merged back to the branch. Review URL: http://codereview.chromium.org/8712 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@4195 0039d316-1c4b-4281-b951-d872f2087c98
* Build a bunch more of chrome/ on Linux.deanm@google.com2008-09-191-2/+0
| | | | | | Patch from Pawel Hajdan Jr. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@2408 0039d316-1c4b-4281-b951-d872f2087c98
* Use a more compact license header in source files.license.bot2008-08-241-29/+4
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@1287 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup a few files, reduce the number of includes.maruel@google.com2008-08-121-0/+1
| | | | | | | | Applied glint. No code change, just moving around. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@713 0039d316-1c4b-4281-b951-d872f2087c98
* Add chrome to the repository.initial.commit2008-07-261-0/+192
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-18 05:13:13 +0000