Home
last modified time | relevance | path

Searched refs:change (Results 1 – 25 of 124) sorted by relevance

12345

/sqlite-3.40.0/ext/session/
H A Dchangesetfuzz.c1106 FuzzChange change; in fuzzDoOneFuzz() local
1112 rc = fuzzSelectChange(pParse, &change); in fuzzDoOneFuzz()
1125 if( change.iGroup==iGrp ){ in fuzzDoOneFuzz()
1126 if( change.eType==FUZZ_GROUP_DEL ){ in fuzzDoOneFuzz()
1130 else if( change.eType==FUZZ_GROUP_DUP ){ in fuzzDoOneFuzz()
1141 if( iGrp==change.iGroup ){ in fuzzDoOneFuzz()
1142 if( change.eType==FUZZ_COLUMN_ADD in fuzzDoOneFuzz()
1143 || change.eType==FUZZ_COLUMN_ADDPK in fuzzDoOneFuzz()
1148 iPKDel = pGrp->aPK[change.iDelete]; in fuzzDoOneFuzz()
1157 if( iGrp!=change.iGroup || i!=change.iDelete ){ in fuzzDoOneFuzz()
[all …]
H A Dsessionstat1.test196 set change [S changeset]
200 set ret [sqlite3changeset_concat $ret $change]
202 set ret $change
H A Dsession9.test224 # Test that if a change that affects FK processing is not applied
256 # Test that if a DELETE change cannot be applied due to an
H A Dsession2.test310 # correctly within changesets. The indirect flag is set for a change
315 # * The change was made by a trigger.
318 # change is considered indirect only if all changes meet the criteria
536 # each change in the changeset.
/sqlite-3.40.0/test/
H A Dexclusive2.test100 # does not modify the freelist, then reset the pager change-counter
104 # It can't tell the db has changed because we reset the change-counter.
105 # 9: Increment the change-counter.
107 # sees the change-counter has been incremented and discards the
190 # 5-6: Modify the dataase change-counter. Connection 1 still works
192 # change-counter.
194 # SQLite detects the modified change-counter and discards the
262 # These tests - exclusive2-3.X - verify that the pager change-counter
263 # is only incremented by the first change when in exclusive access
264 # mode. In normal mode, the change-counter is incremented once
H A Djrnlmode3.test74 # that we cannot change journal_mode while a transaction is active.
81 # Skip the no-change cases
103 # Start a transaction and try to change the journal mode within
124 # Now change the journal mode again. This time the new mode
H A Dcapi3d.test148 # possibility that the statement might change the database file.
151 # statement will change the database file.
171 # change the configuration of a database connection, they do not make
200 # statement would change the database file through side-effects: SELECT
202 # not change the database file directly, sqlite3_stmt_readonly() would
H A Dcrash8.test77 # persistent-journal mode, makes a large change to the database file
80 # a smaller change that requires only a single journal-header to be
81 # written to the journal file. The second change is such that the
84 # first, successful, change. The second process crashes before it can
85 # commit its second change.
89 # and subsequent journal-headers written by the first, successful, change.
H A De_wal.test98 # to change the locking mode using "PRAGMA locking_mode=NORMAL;" are
111 # EVIDENCE-OF: R-63522-46088 The only way to change out of EXCLUSIVE
112 # locking mode is to first change out of WAL journal mode.
217 # EVIDENCE-OF: R-02535-05811 One can explicitly change out of WAL mode
H A Duserauth01.test102 # Any user can change their own password.
123 # No user may change their own admin privilege setting.
138 # The sqlite3_user_change() interface can be used to change a users
166 # Only an admin user can change another users login
H A Ddataversion1.test29 # The data version does not change by ATTACH or by changes to
41 # The data version does change when SQL modifies the table
H A DsharedA.test145 # Create a prepared statement on db2 that will attempt a schema change
159 # schema change when db1 accesses the journal file of test2.db.
186 # schema change.
H A Drdonly.test81 # write-version of the file (and the change-counter, so that the
89 hexio_write test.db 24 11223344 ; # change-counter
H A Dalias.test21 # Aliases are currently evaluated twice. We might try to change this
130 # twice in the current implementation. This might change in the future.
H A Dschema2.test37 # change a collation sequence or user-function while SQL statements
228 # other database connections are aware of the schema change.
230 # other database connections are aware of the schema change.
H A Dptrchng.test53 # never change regardless of what type conversions occur.
123 # should change sometimes.
H A Dio.test78 # and page 1 (db change-counter page).
94 # of abc and the change-counter page.
115 # write to 3 pages to do this: the change-counter, the root-page and
151 # written because page 1 - the change-counter page - is written using
164 # Test that the journal file is not created and the change-counter is
H A Dcapi2.test213 # Update for v3 - the change has not actually happened until the query is
215 # (Later:) The change now happens just before SQLITE_DONE is returned.
232 # Update for v3: Preparing a statement does not affect the change counter.
233 # (Test result changes from 0 to 1). (Later:) change counter updates occur
622 # Update for version 3: A SELECT statement no longer resets the change
H A Dschema.test37 # change a collation sequence or user-function while SQL statements
239 # other database connections are aware of the schema change.
241 # other database connections are aware of the schema change.
H A Dfts3prefix.test153 INSERT INTO t2 VALUES('to change. On 27 September the Norman fleet');
164 INSERT INTO t2 VALUES('to change. On 27 September the Norman fleet');
218 # adding prefix=0 does not change the contents of the %_segdir table.
H A Dmalloc.test728 # When written, this test provoked an obscure change-counter bug.
731 # after the database file change-counter has been written but
736 # the malloc failure and rollback, the change counter will not
765 # the malloc failure occurs after updating the change counter but
776 # the change-counter left as it is.
785 # one of the magic iterations and the change counter was not modified,
H A Danalyze5.test175 # No longer valid due to an EXPLAIN QUERY PLAN output format change
222 # No longer valid due to an EXPLAIN QUERY PLAN format change
H A Dpagerfault3.test46 # Now do the page-size change and VACUUM with IO error injection. When
/sqlite-3.40.0/ext/userauth/
H A Duser-auth.txt31 const char *zUsername, /* Username to change */
113 The sqlite3_user_change() interface can be used to change a users
114 login credentials or admin privilege. Any user can change their own
115 password. Only an admin user can change another users login
116 credentials or admin privilege setting. No user may change their own
/sqlite-3.40.0/doc/
H A Dpager-invariants.txt25 number consists of a single page change.
59 method is a no-op, but that does not change the fact the SQLite will

12345