Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backslashes stored incorrectly in __db_version__ #33

Open
dsinn opened this issue Feb 23, 2016 · 0 comments
Open

Backslashes stored incorrectly in __db_version__ #33

dsinn opened this issue Feb 23, 2016 · 0 comments

Comments

@dsinn
Copy link

dsinn commented Feb 23, 2016

The backslashes get unescaped twice before entering the database.

For example, if I have
INSERT INTOtableNameVALUES('\\\\my\\\\namespace');
then it will enter db_version.sql_up or sql_down as
INSERT INTOtableNameVALUES('\my\namespace');

This is especially problematic if backslashes appear in sql_down, as running with --force-files will cause different queries to be executed even when there are no changes to the migration file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant