Searched refs:changed (Results 1 – 25 of 67) sorted by relevance
123
16 # Note 3: LIRID is changed within the context of a trigger,18 # Note 4: LIRID is not changed by an insert into a view (since everything28 # LIRID changed properly after an insert into a table93 # LIRID changed properly after an insert into table containing an after trigger114 # LIRID changed properly by insert within context of after insert trigger131 # LIRID not changed after an update onto a table containing an after trigger153 # LIRID changed properly by insert within context of after update trigger195 # LIRID changed properly by insert within context of instead of trigger213 # LIRID not changed after a delete on a table containing a before trigger237 # LIRID changed properly by insert within context of delete trigger[all …]
17 # Note 2: changes() is changed within the context of a trigger much like 20 # Note 3: changes() is not changed by a change to a view (since everything74 # changes() set properly after update on table where no rows changed102 # changes() changed properly after insert into table containing after trigger125 # changes() changed properly by update within context of after insert trigger146 # changes() changed properly after update into table containing after trigger168 # changes() changed properly by delete within context of after update trigger178 # changes() changed properly on delete from table containing before trigger200 # changes() changed properly by insert within context of before delete trigger
13 # the journal_mode can only be changed at appropriate times and that29 # journal_mode is changed after the first transaction is undefined and hence
188 #} {1 {database schema has changed}}251 # } {1 {database schema has changed}}305 #} {1 {database schema has changed}}
13 # in a compound select in a case where the source register might be changed
24 # it so that if the page-size is changed to 1024 bytes and the db vacuumed,
29 # use cached pages even if the database is changed on disk. This doesn't104 # It can't tell the db has changed because we reset the change-counter.
19 # VDBE program, as the function might have changed the encoding.
14 # the table being changed. Ticket #2832 shows that in
165 # may be changed by using the page_size and/or pragma auto_vacuum177 # auto_vacuum support property can be changed using VACUUM.
105 SQLITE_SCHEMA {database schema has changed}
55 # of the virtual tables when m is changed.
798 SQLITE_SCHEMA {database schema has changed} \1211 # sqlite3_prepare_v2()) and the schema has changed.1226 } {database schema has changed}1237 } {database schema has changed}
69 # but that has changed. The following tests used to cause errors but now
191 } {SQLITE_SCHEMA {database schema has changed}}
37 # If the 16-byte header is changed, the file will not open
232 # Check that if the definition of a collation sequence is changed and
127 } {1 {database schema has changed}}
140 # changed from "t1" to "t4". The behavior of (1) and (3) match with
273 } {1 {database schema has changed}}
150 # a shared-memory wal-index, the locking mode can be changed freely
48 pages can be changed arbitarily without effecting the logical equivalence63 of bytes from 24 through 39 inclusive will be changed prior to releasing
50 header. The wal-index file itself may not be changed
320 svn info --show-item last-changed-revision >>$(srcdir)/manifest.uuid) || \
192 # Check the values of data-version have not magically changed.