migration option historyTableSchema

[vukbgit]

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]

Thanks for reporting @vukbgit .

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