Documentation Source Text

Check-in [ad008410e6]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Added the "appreq.html" document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ad008410e6eb503f1578cc81b3e0cf704d712e1a
User & Date: drh 2008-07-22 17:20:09
Context
2008-07-22
17:22
(no comment) check-in: 906aef1f58 user: dan tags: trunk
17:20
Added the "appreq.html" document. check-in: ad008410e6 user: drh tags: trunk
17:08
Revert capi3ref.in to scan sqlite3.h instead of sqlite3.c. check-in: 1c87d6c3f1 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Added pages/appreq.in.































































>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
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
<title>Assumptions</title>

<h2>Assumptions Made By SQLite</h2>

<p>This document defines behavior that SQLite expects from the application
that is using SQLite.  We call these "assumptions", but they might also be
called "Application Requirements" since they can be thought of additional
requirements that are imposed on any application that uses SQLite.</p>

<p>Another way of looking at these invariants is that they are limitations
or constraints on the use of SQLite.  If an application fails to abide by
the assumptions described here, then the behavior of SQLite will be
undefined and probably undesirable.</p>

<p>Yet another way of thinking about these invariants is that all of the
statements listed below must be true in order for SQLite to operate correctly.
</p>

<table cellspacing="20">
<tcl>
foreach id [lsort [array names ALLREQ A*]] {
  hd_puts "<tr><td valign=\"top\">$id</td><td valign=\"top\">"
  if {$ALLREQ_VERBATIM($id)} {
    hd_puts $ALLREQ($id)
  } else {
    hd_resolve $ALLREQ($id)
  }
  hd_puts "</td></tr>"
}
</tcl>
</table>