You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
When executing an SQL containing the default placeholder ${ and }, flyway will try to resolve it to a value. However, we're not using placeholders so they shouldn't be resolved. Currently the migration fails with a "No value provided for placeholder expressions" error.
It would be nice to configure flyway to disable placeholder resolution.
P.S.: I know I'm able to configure flyway to use another placeholder pre-and suffix, but this looks more like a hack to me instead of a real solution for this situation.
The text was updated successfully, but these errors were encountered:
When executing an SQL containing the default placeholder ${ and }, flyway will try to resolve it to a value. However, we're not using placeholders so they shouldn't be resolved. Currently the migration fails with a "No value provided for placeholder expressions" error.
It would be nice to configure flyway to disable placeholder resolution.
P.S.: I know I'm able to configure flyway to use another placeholder pre-and suffix, but this looks more like a hack to me instead of a real solution for this situation.
The text was updated successfully, but these errors were encountered: