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

OracleTableJournal ignores schema name #4

Open

nvarscar opened this issue Jan 19, 2019 · 0 comments

Labels

bug

nvarscar commented Jan 19, 2019

Neither OracleTableJournal.CreateSchemaTableSql()
https://github.com/DbUp/DbUp/blob/976d91cd5e4bc7c478f172e91b597dd1495274de/src/dbup-oracle/OracleTableJournal.cs#L33
nor OracleTableJournal.DoesTableExistSql()
https://github.com/DbUp/DbUp/blob/976d91cd5e4bc7c478f172e91b597dd1495274de/src/dbup-oracle/OracleTableJournal.cs#L77
take SchemaTableSchema (schema name) into account, as compared to TableJournal.DoesTableExistSql():
https://github.com/DbUp/DbUp/blob/976d91cd5e4bc7c478f172e91b597dd1495274de/src/dbup-core/Support/TableJournal.cs#L215

As a result, versions table gets deploy to the current schema regardless of the schema parameter value.

The text was updated successfully, but these errors were encountered:

mjauernig added the bug label

droyad transferred this issue from DbUp/DbUp

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