File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (14 lines) | stat: -rw-r--r-- 838 bytes parent folder | download | duplicates (9) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
 
The webdata component manages the "web database", a SQLite database stored in
the user's profile containing various webpage-related metadata such as autofill
and web search engine data. A single database (per profile) is shared by many
unrelated features.

**If you are adding data storage for a [new] feature and want to use SQLite, you
should probably default to creating a unique database using the compat layer in
[`//sql`](https://source.chromium.org/chromium/chromium/src/+/main:sql/).**
See [SQLite is a local optimum for Chromium](https://bit.ly/3Xc3EcH).

This component is not allowed to depend on content/, because it is used by iOS.
If dependencies on content/ need to be added, this component will have to be
made into a layered component: see
https://www.chromium.org/developers/design-documents/layered-components-design .