openvsx
openvsx copied to clipboard
Flyway migration scripts hardcoded public schema
Issue
The flyway migration scripts hard code the public schema for every table. This makes it impossible to use a different schema without modifying the migration scripts.
Suggested Solution
The migration scripts should not specify a schema. Rather, the application should default to using the public schema if a schema is not specified.
I agree. But I don't know whether it's possible to change this such that Flyway accepts the modified migrations on existing deployments.