You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Synthetic first migration example for demonstration.
-- migrate:upCREATESCHEMAIF NOT EXISTS up;
-- migrate:downCREATESCHEMAIF NOT EXISTS down;
On Windows, the first migration will always be rolled back and both schemes will appear in the database.
On Linux all is fine.
This behavior was seen only in the first migration. If you add a migration before it, even one consisting of only comments, the down schema will not be created.
! UPDATE:
I figured out what was causing the poblem. These are Windows line breaks (\r\n). I attach a file created on Windows, with it the same behavior occurs under Linux.
The text was updated successfully, but these errors were encountered:
* chore: add failing tests that demonstrate the issue
* fix: correct migration parsing regexps
Fixes#213.
* fix: satisfy linter
* fix: use unique test table names in test migrations
20210329163410_initial_migration.txt
Synthetic first migration example for demonstration.
On Windows, the first migration will always be rolled back and both schemes will appear in the database.
On Linux all is fine.
This behavior was seen only in the first migration. If you add a migration before it, even one consisting of only comments, the
down
schema will not be created.! UPDATE:
I figured out what was causing the poblem. These are Windows line breaks (\r\n). I attach a file created on Windows, with it the same behavior occurs under Linux.
The text was updated successfully, but these errors were encountered: