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

Oracle SQL/Plus DEFINE should not be case sensitive. #2115

Closed
matthew-sprague opened this issue Aug 23, 2018 · 1 comment
Closed

Oracle SQL/Plus DEFINE should not be case sensitive. #2115

matthew-sprague opened this issue Aug 23, 2018 · 1 comment

Comments

@matthew-sprague
Copy link

@matthew-sprague matthew-sprague commented Aug 23, 2018

Which version and edition of Flyway are you using?

5.1.4 pro trial

If this is not the latest version, can you reproduce the issue with the latest one as well?

(Many bugs are fixed in newer releases and upgrading will often resolve the issue)

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

Command-line

Which database are you using (type & version)?

OracleXE 11.2g

Which operating system are you using?

Windows 7 enterprise

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)

--works case insensitive
set define on

--works case insensitive
set define ~
--doesn't work case sensitive
define random="--"

--works case sensitive when uncommented
--DEFINE random="--"

declare

   --
    --    For service locations with a single extract location, simply assign every client in the service location to that extract location.
    --
    PROCEDURE proc( ) IS
    BEGIN

        dbms_output.put_line('test replacement ~random ');
        
    END;
	
begin
	dbms_output.enable(null);
    
end;
/
What did you expect to see?

~random be set to "--" and successful migration

What did you see instead?

12:33:57,138 ERROR [Main] No value provided for placeholder expressions: ~random. Check your configuration!

@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Aug 24, 2018

Thank you for reporting and thanks for the detailed analysis. This was a big help in finding and fixing the issue. The fix will be out as part of the next release.

Loading

axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants