-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Flyway multiple datasource migration does not work on native #7685
Comments
Could you provide a small reproducer? Thanks! |
|
@machi1990 do you think you could have a look at that one? |
@gsmet I am just seeing the ping now. I'll have a look over the coming days. |
The QuarkusPathLocationScanner returned all migrations locations by default, this risked to cause collision when we have a same filename for a migration script which is handled by different datasources - a behaviour encountered on the issue quarkusio#7685. Let's avoid this case by making sure that the scanner only returns migration that it can recognize. Fixes quarkusio#7685
@gsmet I had a couple of hours with which I have opened #8065. The PR once merged should fix the issue @yanxuehe |
The QuarkusPathLocationScanner returned all migrations locations by default, this risked to cause collision when we have a same filename for a migration script which is handled by different datasources - a behaviour encountered on the issue quarkusio#7685. Let's avoid this case by making sure that the scanner only returns migration that it can recognize. Fixes quarkusio#7685
The QuarkusPathLocationScanner returned all migrations locations by default, this risked to cause collision when we have a same filename for a migration script which is handled by different datasources - a behaviour encountered on the issue quarkusio#7685. Let's avoid this case by making sure that the scanner only returns migration that it can recognize. Fixes quarkusio#7685
The QuarkusPathLocationScanner returned all migrations locations by default, this risked to cause collision when we have a same filename for a migration script which is handled by different datasources - a behaviour encountered on the issue quarkusio#7685. Let's avoid this case by making sure that the scanner only returns migration that it can recognize. Fixes quarkusio#7685
The below is the application.properties
it works on jdk 8.
not on graalvm 19.3.1
the error is
if i change the sql files with different versions.
then all the sql files will be executed for all the data sources
The text was updated successfully, but these errors were encountered: