Home
last modified time | relevance | path

Searched refs:process (Results 1 – 25 of 80) sorted by relevance

1234

/sqlite-3.40.0/test/
H A Dlock2.test24 # lock2-1.1: Connect a second process to the database.
25 # lock2-1.2: Establish a RESERVED lock with this process.
26 # lock2-1.3: Get a SHARED lock with the second process.
27 # lock2-1.4: Try for a RESERVED lock with process 2. This fails.
28 # lock2-1.5: Try to upgrade the first process to EXCLUSIVE, this fails so
30 # lock2-1.6: Release the SHARED lock held by the second process.
31 # lock2-1.7: Attempt to reaquire a SHARED lock with the second process.
33 # lock2-1.8: Ensure the first process can now upgrade to EXCLUSIVE.
H A Dlock4.test47 # Create a script to drive a separate process that will
54 # Meanwhile, this process will:
58 # C. Commit the changes to test.db thus alloing the other process
63 # Create a script for the second process to run.
90 # Kick off the second process.
93 # Wait until the second process has started its transaction on test2.db.
111 # The other process has committed its transaction on test2.db by
H A Dcrash.test76 } {1 {child process exited abnormally}}
85 } {1 {child process exited abnormally}}
93 } {1 {child process exited abnormally}}
152 } {1 {child process exited abnormally}}
160 } {1 {child process exited abnormally}}
199 } {1 {child process exited abnormally}}
249 } {1 {child process exited abnormally}}
281 } {1 {child process exited abnormally}}
304 } {1 {child process exited abnormally}}
366 } {1 {child process exited abnormally}}
[all …]
H A Dbusy2.test58 # a second connection within process 1. Process 1 now has connections
59 # [db] and [db1.2], process 2 has connection [db2] only.
83 # Take a read lock with [db] in process 1.
92 # Insert a row using [db2] in process 2. Then try a passive checkpoint.
112 # Passive checkpoint with [db1.2] (process 1). No SQLITE_BUSY, returns
121 # Full checkpoint with [db1.2] (process 1). SQLITE_BUSY returned in
H A Dwalcrash.test49 } {1 {child process exited abnormally}}
62 } {1 {child process exited abnormally}}
86 } {1 {child process exited abnormally}}
99 } {1 {child process exited abnormally}}
128 # } {1 {child process exited abnormally}}
157 } {1 {child process exited abnormally}}
200 } {1 {child process exited abnormally}}
242 } {1 {child process exited abnormally}}
284 } {1 {child process exited abnormally}}
H A Dtkt-fc62af4523.test39 # Launch an external process. Have it write (but not commit) a large
57 # Now do "PRAGMA journal_mode = DELETE" in this process. At one point
59 # even though the external process is currently using it.
64 # Cause the external process to crash. Since it has already written
74 } {ERROR: Child process hung up}
H A Dwalcrash2.test23 # existed at one point: If a process crashes mid-transaction, it may have
27 # if the process crashes, the transaction is implicitly rolled back and
33 # non-zero, the next process that attempts to read or write the hash
45 # walcrash2-1.2: Have an external process open a transaction, add 8 entries
51 # database. This should cause the process to go into the
H A Dlock6.test20 # Launch another testfixture process to be controlled by this one. A
22 # 'testfixture' to execute a command. The child testfixture process is shut
34 # Execute a command in a child testfixture process, connected by two-way
52 # process, followed by the word "OVER" on a line of its own. The child
53 # process evaluates the script and writes the results to stdout, followed
H A Dcrash8.test55 # Potential corruption scenario 1. A second process opens the database
60 # When the first process accessed the database again, it was rolling back
62 # was loaded before the second process made its first, successful,
71 } {1 {child process exited abnormally}}
76 # Potential corruption scenario 2. The second process, operating in
84 # first, successful, change. The second process crashes before it can
87 # When the first process accessed the database again, it was rolling back
110 } {1 {child process exited abnormally}}
305 } {1 {child process exited abnormally}}
326 } {1 {child process exited abnormally}}
H A Dwalblock.test67 # 1. Open a write transaction using client [db] in this process.
74 # the other process to read from the database. It should block, as it
78 # process has not answered the request.
81 # Ensure that the second process has by this stage read the database
H A Dbackup_ioerr.test82 # 2) Open a backup process. Set the cache-size for the destination
85 # 3) Step the backup process N times to partially backup the database
86 # file. If an IO error is reported, then the backup process is
114 # 5) Step the backup process to finish the backup. If an IO error is
115 # reported, then the backup process is concluded with a call to
122 # 6) Finish the backup process.
171 # Step 2: Open the backup process.
H A Dunixexcl.test30 # a process-wide exclusive lock is taken on it. This means other connections
31 # within the process may still access the db normally, but connections from
32 # outside the process cannot.
H A Dtemptrigger.test29 # in shared-cache mode. If process 1 connections to a shared-cache and
31 # schema. If process 2 reloads the shared-cache schema from disk, then
32 # it does not recreate the temp trigger belonging to process 1. From the
33 # point of view of process 1, the temp trigger just disappeared.
H A Dtkt4018.test48 # reused, then the process will quickly exceed its maximum number of
58 # having a second process try to write the db.
H A Dwalprotocol2.test22 # When recovering the contents of a WAL file, a process obtains the WRITER
24 # to lock all other bytes (because some other process is holding a read
H A Dcrash7.test76 } {1 {child process exited abnormally}}
111 } {1 {child process exited abnormally}}
H A Dcrash4.test90 set c [list 1 {child process exited abnormally}]
93 } {1 {child process exited abnormally}}
H A Dcrash2.test103 } {1 {child process exited abnormally}}
126 } {1 {child process exited abnormally}}
H A Dtemptable.test151 # occur when process A creates a temporary table T then process B
152 # creates a permanent table also named T. The temp table in process A
H A Dbackcompat.test16 # To use this test, old versions of the testfixture process should be
22 # process located in lock_common.tcl. See the commments in lock_common.tcl
290 # process. Check that the [code2] process can recover the log.
/sqlite-3.40.0/ext/rbu/
H A Drbucrash.test77 # 1. This process starts the rbu update and calls sqlite3rbu_step()
80 # 2. A second process resumes the rbu update and attempts to call
84 # 3. This process attempts to resume the rbu update from whatever
122 if {$res == "1 {child process exited abnormally}"} {
/sqlite-3.40.0/autoconf/tea/
H A DREADME11 and then run make. For more information about the build process, see
24 Msys + Mingw build process. This provides a Unix-style build while
/sqlite-3.40.0/ext/wasm/api/
H A DREADME.md52 Gets created by the build process and populates the
92 process, which is what finally executes the initialization code
98 The build process glues those files together, resulting in
110 The following files are part of the build process but are injected
/sqlite-3.40.0/doc/
H A Dwal-lock.md12 process is blocked by a lower priority one.
24 Wal database "recovery" is a process required when the number of connected
/sqlite-3.40.0/tool/
H A Dbuild-all-msvc.bat31 REM Please note that the SQLite build process performed by the Makefile
54 REM There are a few other environment variables that impact the build process
267 REM NOTE: Check for the external tools needed during the build process ^(i.e.
268 REM those that do not get compiled as part of the build process itself^)
282 REM NOTE: A Tcl shell executable is required during the SQLite build process
633 REM command line tools needed during the build process itself.
703 REM command line tools needed during the build process itself.

1234