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.

Sign up for GitHub

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

Jump to bottom

migration option historyTableSchema #51

Open

vukbgit opened this issue Jul 17, 2023 · 1 comment

Assignees

Labels

bug

vukbgit commented Jul 17, 2023

hello, great tool!
With version 2.4.1 and PostgreSQL: 9.6+ (15.3) if you set migrationOptions.historyTableSchema to a schema different from 'public':

table historyTableSchema.historyTableName is not created into historyTableSchema schema (even if schema exists) but into public schema
when you save a patch (-s parameter)
- if table historyTableSchema.historyTableName exists patch is corretly save into it
- table public.historyTableName is created (but remains empty because patch is correctly saved into historyTableSchema.historyTableName)

michaelsogos self-assigned this

michaelsogos added the bug label

Owner

michaelsogos commented Jun 6, 2024

Thanks for reporting @vukbgit .

Let me fix it and I'll be back soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment