aboutsummaryrefslogtreecommitdiffstats
path: root/package/sqlite/Config.in
blob: 8766786010fb4608522dcc760c76299d335a683f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
config BR2_PACKAGE_SQLITE
	bool "sqlite"
	help
	  SQLite is a small C library that implements a self-contained,
	  embeddable, zero-configuration SQL database engine.

	  http://www.sqlite.org/

config BR2_PACKAGE_SQLITE_READLINE
	bool "Command-line editing"
	depends on BR2_PACKAGE_SQLITE
	select BR2_PACKAGE_NCURSES
	select BR2_PACKAGE_READLINE
	help
	  Enable command-line editing. This requires ncurses and readline.

config BR2_PACKAGE_SQLITE_STAT3
	bool "Additional query optimizations (stat3)"
	depends on BR2_PACKAGE_SQLITE
	help
	  Adds additional logic to the ANALYZE command and to the query
	  planner that can help SQLite to choose a better query plan under
	  certain situations.

config BR2_PACKAGE_SQLITE_ENABLE_FTS3
	bool "Enable version 3 of the full-text search engine"
	depends on BR2_PACKAGE_SQLITE
	help
	  When this option is defined in the amalgamation
	  (see http://www.sqlite.org/amalgamation.html), version 3 of
	  the full-text search engine is added to the build automatically.

config BR2_PACKAGE_SQLITE_ENABLE_UNLOCK_NOTIFY
	bool "Enable sqlite3_unlock_notify() interface"
	depends on BR2_PACKAGE_SQLITE
	help
	  This option enables the sqlite3_unlock_notify() interface and its
	  accosiated functionality. See the documentation
	  http://www.sqlite.org/unlock_notify.html for additional information.

config BR2_PACKAGE_SQLITE_SECURE_DELETE
	bool "Set the secure_delete pragma on by default"
	depends on BR2_PACKAGE_SQLITE
	help
	  This compile-time option changes the default settings of the
	  secure_delete pragma. When this option is not used, secure_delete
	  defaults to off. When this option is present, secure_delete defaults
	  to on.

	  The secure_delete setting causes deleted content to be overwritten
	  with zeros. There is a small performance penalty for this since
	  additional I/O must occur. On the other hand, secure_delete can
	  prevent sensitive information from lingering in unused parts
	  of the database file after it has allegedly been deleted.
	  See the documentation on the
	  http://www.sqlite.org/pragma.html#pragma_secure_delete
	  for additional information.