Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Working on global [...]-style hyperlinks. This is an interim check-in in order to transfer from one machine to another. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
a1c70893c60bfd0166be3ccfa3292509 |
User & Date: | drh 2007-12-16 00:42:24.000 |
Context
2007-12-18
| ||
18:09 | SQLite does not have an ! operator. CVSTrac ticket #2849. (check-in: 253e0c9a09 user: drh tags: trunk) | |
2007-12-16
| ||
00:42 | Working on global [...]-style hyperlinks. This is an interim check-in in order to transfer from one machine to another. (check-in: a1c70893c6 user: drh tags: trunk) | |
2007-12-15
| ||
14:44 | Updates to the distinctive features page. (check-in: ceb449161d user: drh tags: trunk) | |
Changes
Changes to pages/capi3ref.in.
1 2 3 4 5 | 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 | - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + | <title>C/C++ Interface For SQLite Version 3</title> <h2 class=pdf_section>C/C++ Interface For SQLite Version 3</h2> <tcl> |
︙ | |||
31 32 33 34 35 36 37 38 39 40 41 | 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 | + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + | set lx [string trim [string range $line 3 end]] if {[regexp {^CATEGORY: +([a-z]*)} $lx all cx]} { set type $cx } elseif {[regexp {^KEYWORDS: +(.*)} $lx all kx]} { foreach k $kx { set keyword($k) 1 } } elseif {[regexp {^COVENANTS:$} $lx]} { append body "\n<h3>Covenants:</h3>\n" starttab set phase 2 } elseif {[regexp {^LIMITATIONS:$} $lx]} { append body "\n<h3>Limitations:</h3>\n" starttab set phase 2 } else { append body $lx\n } } elseif {[string range $line 0 1]=="*/"} { |
︙ | |||
349 350 351 352 353 354 355 | 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 | - + | set body [subst -novar -noback $body] puts "$body" puts "<hr>" set fkey [lindex $keywords 0] if {![info exists keyword_to_file($fkey)]} { real_puts fkey=$fkey real_puts c=$c |
︙ |
Changes to pages/conflict.in.
1 2 3 4 5 6 7 8 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | - - - + + + - | <title>Constraint Conflict Resolution in SQLite</title> <h1>Constraint Conflict Resolution in SQLite</h1> <p> In most SQL databases, if you have a UNIQUE constraint on a table and you try to do an UPDATE or INSERT that violates the constraint, the database will abort the operation in |
︙ | |||
39 40 41 42 43 44 45 | 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 | - + - - - - - - - - - - - - - - - - - - - - - - - | <dt><b>FAIL</b></dt> <dd><p>When a constraint violation occurs, the command aborts with a return code SQLITE_CONSTRAINT. But any changes to the database that the command made prior to encountering the constraint violation are preserved and are not backed out. For example, if an UPDATE statement encountered a constraint violation on the 100th row that it attempts to update, then the first 99 row changes are preserved |
Deleted pages/requirements.in.
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
|
Added pages/specification.in.