dbmate 2.8.0 → 2.9.0

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.
Files changed (3) hide show
  1. package/README.md +3 -1
  2. package/dist/resolveBinary.js.map +1 -1
  3. package/package.json +8 -8
package/README.md CHANGED
@@ -129,6 +129,7 @@ dbmate rollback # roll back the most recent migration
129
129
  dbmate down # alias for rollback
130
130
  dbmate status # show the status of all migrations (supports --exit-code and --quiet)
131
131
  dbmate dump # write the database schema.sql file
132
+ dbmate load # load schema.sql file to the database
132
133
  dbmate wait # wait for the database server to become available
133
134
  ```
134
135
 
@@ -138,6 +139,7 @@ The following options are available with all commands. You must use command line
138
139
 
139
140
  - `--url, -u "protocol://host:port/dbname"` - specify the database url directly. _(env: `DATABASE_URL`)_
140
141
  - `--env, -e "DATABASE_URL"` - specify an environment variable to read the database connection URL from.
142
+ - `--env-file ".env"` - specify an alternate environment variables file(s) to load.
141
143
  - `--migrations-dir, -d "./db/migrations"` - where to keep the migration files. _(env: `DBMATE_MIGRATIONS_DIR`)_
142
144
  - `--migrations-table "schema_migrations"` - database table to record migrations in. _(env: `DBMATE_MIGRATIONS_TABLE`)_
143
145
  - `--schema-file, -s "./db/schema.sql"` - a path to keep the schema.sql file. _(env: `DBMATE_SCHEMA_FILE`)_
@@ -408,7 +410,7 @@ When you run the `up`, `migrate`, or `rollback` commands, dbmate will automatica
408
410
 
409
411
  It is recommended to check this file into source control, so that you can easily review changes to the schema in commits or pull requests. It's also possible to use this file when you want to quickly load a database schema, without running each migration sequentially (for example in your test harness). However, if you do not wish to save this file, you could add it to your `.gitignore`, or pass the `--no-dump-schema` command line option.
410
412
 
411
- To dump the `schema.sql` file without performing any other actions, run `dbmate dump`. Unlike other dbmate actions, this command relies on the respective `pg_dump`, `mysqldump`, or `sqlite3` commands being available in your PATH. If these tools are not available, dbmate will silenty skip the schema dump step during `up`, `migrate`, or `rollback` actions. You can diagnose the issue by running `dbmate dump` and looking at the output:
413
+ To dump the `schema.sql` file without performing any other actions, run `dbmate dump`. Unlike other dbmate actions, this command relies on the respective `pg_dump`, `mysqldump`, or `sqlite3` commands being available in your PATH. If these tools are not available, dbmate will silently skip the schema dump step during `up`, `migrate`, or `rollback` actions. You can diagnose the issue by running `dbmate dump` and looking at the output:
412
414
 
413
415
  ```sh
414
416
  $ dbmate dump
package/dist/resolveBinary.js.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"resolveBinary.js","sourceRoot":"","sources":["../src/resolveBinary.ts"],"names":[],"mappings":";;;AAAA,+CAA8C;AAE9C;;KAEK;AACL,SAAgB,aAAa;IAC3B,MAAM,GAAG,GAAG,uBAAQ,KAAK,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/C,MAAM,IAAI,GAAG,WAAW,uBAAQ,IAAI,mBAAI,cAAc,GAAG,EAAE,CAAC;IAE5D,IAAI;QACF,OAAO,OAAO,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;KAC9B;IAAC,OAAO,GAAG,EAAE;QACZ,IACE,GAAG,IAAI,SAAS;YAChB,OAAO,GAAG,KAAK,QAAQ;YACvB,MAAM,IAAI,GAAG;YACb,GAAG,CAAC,IAAI,KAAK,kBAAkB,EAC/B;YACA,MAAM,IAAI,KAAK,CAAC,mCAAmC,IAAI,GAAG,CAAC,CAAC;SAC7D;aAAM;YACL,MAAM,GAAG,CAAC;SACX;KACF;AACH,CAAC;AAlBD,sCAkBC"}
1
+ {"version":3,"file":"resolveBinary.js","sourceRoot":"","sources":["../src/resolveBinary.ts"],"names":[],"mappings":";;;AAAA,+CAA8C;AAE9C;;KAEK;AACL,SAAgB,aAAa;IAC3B,MAAM,GAAG,GAAG,uBAAQ,KAAK,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/C,MAAM,IAAI,GAAG,WAAW,uBAAQ,IAAI,mBAAI,cAAc,GAAG,EAAE,CAAC;IAE5D,IAAI,CAAC;QACH,OAAO,OAAO,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;IAC/B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,IACE,GAAG,IAAI,SAAS;YAChB,OAAO,GAAG,KAAK,QAAQ;YACvB,MAAM,IAAI,GAAG;YACb,GAAG,CAAC,IAAI,KAAK,kBAAkB,EAC/B,CAAC;YACD,MAAM,IAAI,KAAK,CAAC,mCAAmC,IAAI,GAAG,CAAC,CAAC;QAC9D,CAAC;aAAM,CAAC;YACN,MAAM,GAAG,CAAC;QACZ,CAAC;IACH,CAAC;AACH,CAAC;AAlBD,sCAkBC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dbmate",
3
- "version": "2.8.0",
3
+ "version": "2.9.0",
4
4
  "description": "A lightweight, framework-agnostic database migration tool",
5
5
  "repository": "https://github.com/amacneil/dbmate",
6
6
  "homepage": "https://github.com/amacneil/dbmate#readme",
@@ -24,12 +24,12 @@
24
24
  "build": "tsc --build"
25
25
  },
26
26
  "optionalDependencies": {
27
- "@dbmate/linux-ia32": "2.8.0",
28
- "@dbmate/linux-x64": "2.8.0",
29
- "@dbmate/linux-arm": "2.8.0",
30
- "@dbmate/linux-arm64": "2.8.0",
31
- "@dbmate/darwin-x64": "2.8.0",
32
- "@dbmate/darwin-arm64": "2.8.0",
33
- "@dbmate/win32-x64": "2.8.0"
27
+ "@dbmate/linux-ia32": "2.9.0",
28
+ "@dbmate/linux-x64": "2.9.0",
29
+ "@dbmate/linux-arm": "2.9.0",
30
+ "@dbmate/linux-arm64": "2.9.0",
31
+ "@dbmate/darwin-x64": "2.9.0",
32
+ "@dbmate/darwin-arm64": "2.9.0",
33
+ "@dbmate/win32-x64": "2.9.0"
34
34
  }
35
35
  }