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

Incorrect Redshift search_path parsing #1831

Closed
joshyaustin opened this issue Nov 15, 2017 · 0 comments
Closed

Incorrect Redshift search_path parsing #1831

joshyaustin opened this issue Nov 15, 2017 · 0 comments

Comments

@joshyaustin
Copy link

What version of Flyway are you using?

4.2.0

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)

Java API- flyway-core-4.2.0

What database are you using (type & version)?

amazon redshift

What operating system are you using?

OSX, linux

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
When flyway DB migration is initiated in a java-spring-boot application connecting to Amazon Redshift DB using redshift DB driver, it parses out the schema name wrongly.

flyway-core-4.2.0] Flyway.java 811 : originalSchema variable value is "$user",public
org.flywaydb.core.internal.dbsupport.redshift.RedshiftDbSupport.getOriginalSchema() // line 37
extracts "ublic" instead of "public" (the leading 'p' is stripped).

What did you expect to see?

schema name should be parsed correctly ("public" in this case)

What did you see instead?

org.flywaydb.core.internal.dbsupport.redshift.RedshiftDbSupport.getOriginalSchema() // line 37
extracts "ublic" instead of "public" (the leading 'p' is stripped)

@axelfontaine axelfontaine added this to the Flyway 5.0.0 milestone Nov 15, 2017
@axelfontaine axelfontaine changed the title Flyway amazon redshift support library parses the schema name wrong Incorrect Redshift search_path parsing Nov 15, 2017
axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Nov 15, 2017
dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants