jasondcamp / pyway Goto Github PK

I'm looking to use Pyway with SQLExpress, and other forms of SQLServer, are there any plans for adding support for this, or a reason why it wasn't included in the beginning.

Happy to do the work and submit a PR if desired (Contribution guidelines suggested raising an issue first)

If the checksums do not match, but the filenames/versions are already in the database, it will still try to apply starting with 1.01. Major issue, need to look into why this is failing.

Hello,

I'm trying to integrate pyway in a project which needs SQL migration.

I am trying to integrate files with patterns like : V5.0_01__initial_schema.sql
However, the version in pyway schema table gives me : 0.01... I would need it to be 5.0.01 ({major}.{minor}). If I write a dot in major version (ex: V5.0), it seems the extension is not SQL anymore, but the name of the script (in my case : 0_01__INITIAL_SCHEMA)...

Could you please look to consider this evolution ?
Thank you 🙂

I'm trying to integrate pyway in an existing project that previously used Flyway.

The sql patchs of this project follows the pattern needed for pyway for the most part except for the minor version: they start at 1 (without a 0 in front) and may exeed 99.

I see here that this minor version is strictly limited to 2 numbers.

Would it be possible to remove this limitation please?

Currently pinned version of PyYAML is outdated and not installable anymore.

Requirements need to be updated to use the latest PyYAML.

To create or update roles the passwords needs to be passed as a parameter for security reasons .

Example
CREATE ROLE read_only WITH LOGIN PASSWORD '${password}' VALID UNTIL '${validUntil}';

Right now you need to specify the specific file, lets let it take a path and we can parse out the filename from the path, makes it easier to run the import command.

Annoying display issue but version 1.10 displays as 1.1 - fix.

We missed an issue with SQL in the postgres factory, because we're not testing against postgres. Work on this.

I got started with flyway (because I used it back in the day in some project and it nicely did it's thing), then realised that it's semi-ideal in a python app. Some searching landed me on pyway.

It would be nice to be greeted in the docs with a "Migrating from flyway to pyway? Do this:" type of thing. Now I am not sure (but pretty sure ;) ) if pyway requires any changes to the sql baseline schema and/or migrations. And for instance the table I have in my schema to track the version it's on, is that okay or does it need work?

thanks in advance!

Add 3.12 support for tests and updating pypi

Is import meant to replace baseline or is baseline on the roadmap?

Hello,

Is it possible to use environment variables in the .pyway.conf file. I want to do something like:

database_type: postgres
database_username: ${DB_USER}
database_password: ${DB_PASSWORD}
database_host: ${DB_HOST}
database_port: ${DB_PORT}
database_name: ${DB_DBNAME}
database_migration_dir: infra/pyway
database_table: public.pyway

I get the following error : invalid integer value "${ELI_DB_PORT}" for connection option "port"
Is it something supported with another syntax or not supported at all?

Thanks
Julien

Unclear why this was written or why its marked as xfail :) Try to remember what I was trying to do there.

When someone converts newlines to windows format for example, it messes up the checksums. Think about how to handle this.

Add a validate before a migrate, and don't do the migration if the validation fails

Sometimes, especially when developing, you might need to update the checksum due to it changing but your migration was still run and valid against the db. Add a method to update only the checksum even though the migration is already applied. Do not apply it again.

Initial deploy bombs out because validation fails on first run before the database is populated. Added a skip_errors option that will silently pass through validation if set, so we can continue the migration process.