genesis-stack 1.4.9 → 1.4.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -50,7 +50,8 @@ Rails SQLite connection, Active Record migration, and database filename conventi
|
|
|
50
50
|
its schema and migrates an existing one.
|
|
51
51
|
- The `sqlite3` gem normally installs a precompiled native gem; a source build
|
|
52
52
|
needs the SQLite headers. Use the inherited Rails migration and seed
|
|
53
|
-
guidance and test
|
|
53
|
+
guidance, and run a path's two-writer test, where it needs one, on SQLite
|
|
54
|
+
itself.
|
|
54
55
|
- Sanity checks with Rails and SQLite: the rails and sqlite pieces' checks
|
|
55
56
|
apply.
|
|
56
57
|
|
package/stacks/pieces/sqlite.md
CHANGED
|
@@ -30,9 +30,9 @@ SQLite file-backed persistence, migrations, and backup conventions.
|
|
|
30
30
|
- Keep durable database files outside disposable build and release directories.
|
|
31
31
|
A host may supply a persistent filename; do not replace that value with a
|
|
32
32
|
repository-relative default or recreate an existing database during setup.
|
|
33
|
-
- Use transactions, foreign-key enforcement, and bounded busy handling.
|
|
34
|
-
|
|
35
|
-
SQLite's locking behavior.
|
|
33
|
+
- Use transactions, foreign-key enforcement, and bounded busy handling. Run a
|
|
34
|
+
path's two-writer test, where it needs one, on SQLite itself; a different
|
|
35
|
+
engine does not establish SQLite's locking behavior.
|
|
36
36
|
- Use SQLite's online backup API or `VACUUM INTO` for a consistent backup of a
|
|
37
37
|
running database, including committed WAL data. Do not copy only the main file
|
|
38
38
|
while writers are active. Validate backups and prove restoration before
|