Searched refs:answer (Results 1 – 25 of 33) sorted by relevance
12
25 set answer {}28 lappend answer "CREATE INDEX"31 lappend answer "a=$a"33 set answer
110 unset -nocomplain id data1 data2 jointype onclause whereclause answer111 foreach {id data1 data2 jointype onclause whereclause answer} {191 } $answer195 } $answer
147 set answer {}152 lappend answer $j $r158 } $answer
63 # query, the wrong answer results:69 # Constant propagation caused an incorrect answer in the following
22 # correct answer.65 # should give exactly the same answer.214 # should give exactly the same answer.349 # should give exactly the same answer.
140 proc maketest {tnum sql answer} { argument145 puts "\175 {$answer}"
15 # it gets the wrong answer...
24 # correct answer.
85 # disabled. Should give the exact same answer.
20 # generate the same answer. But the third one does not. It is as if the
22 # correct answer.
23 # correct answer.
275 # answer if we try to convert this non-existant localtime to utc?474 # same answer.
145 # right answer.
159 # For SQLite version 3.7.17 the answer was two rows, which is wrong.
89 # Same answer with other formulations of the same query
175 # incorrect answer.
105 set answer [split [string repeat "ottffs" 128] ""]106 faultsim_test_result [list 0 $answer]109 if {$res != $answer} { error "Database content appears incorrect ($res)" }
419 # Both queries should generate the same results so the answer should
536 # Both queries should generate the same results so the answer should695 # to 200. The following tests still run, but the answer is now
58 The following algorithm always compute the correct answer. However, this73 The following procedure computes the same answer as the simple full-scan
46 are said to be "logically equivalent" if they give the same answer to
26 * The ->> operator converts the answer into a primitive SQL datatype
922 # EVIDENCE-OF: R-32761-23915 One would get the same answer without the948 # answer itself, it merely limited the search space.