mirror of https://github.com/not-kennethreitz/records-migrate.git synced 2026-06-05 06:56:14 +00:00

T

dependabot[bot] 21d57d5c36 Bump pyyaml from 4.2b4 to 5.4

Bumps [pyyaml](https://github.com/yaml/pyyaml) from 4.2b4 to 5.4.
- [Release notes](https://github.com/yaml/pyyaml/releases)
- [Changelog](https://github.com/yaml/pyyaml/blob/master/CHANGES)
- [Commits](https://github.com/yaml/pyyaml/commits/5.4)

Signed-off-by: dependabot[bot] <support@github.com>

2021-04-20 19:41:37 +00:00

migrations

changes

2019-02-01 09:27:37 -05:00

records_migrate

fixes

2019-02-02 08:17:07 -05:00

.gitignore

empty setup.py

2019-02-01 08:28:27 -05:00

LICENSE

Initial commit

2019-02-01 07:59:54 -05:00

Pipfile

updates

2019-02-02 08:10:11 -05:00

Pipfile.lock

Bump pyyaml from 4.2b4 to 5.4

2021-04-20 19:41:37 +00:00

README.md

updates

2019-02-02 08:10:11 -05:00

setup.py

empty setup.py

2019-02-01 08:28:27 -05:00

t.py

updates

2019-02-02 08:10:11 -05:00

README.md

Records-Migrate: a migration system for Records

A migration system for the Records Python library.

Intented Usage

Assuming DATABASE_URL is set:

$ records-migrate check
all migrations appear to be applied!

$ records-migrate new
Created file migrations/0003.sql. Feel free to add a suffix to the file name.

$ records-migrate apply
Applied migration 3/5...,,

$ records-migrate schema
Dumps out SQL script for generating the schema.

Considerations

Don't base migration order on file creation time, as Heroku strips the data on deploy.