Add Oracle SQLPlus syntax for substitution variables

Jon,

could you add at least a valid example, just something as simple as "select 1;", where the "1" should be the variable, so we can write a proper unit-test.
A link to some reference might help as well. We could add this to the documentation of the plugin.

sql plugin should stay neutral as much as possible and adding oracle specific to the parser may not a good idea

Yes, it must stay neutral, but what's the problem with giving the option to change the Interpolator?
By default use the MavenInterpolator, developers could change it. But don't mix interpolators, just pick one.

DROP SEQUENCE &&schema..ACCOUNT_CODE_DEFINITION_SEQ;
would become
DROP SEQUENCE SOME_SCHEMA.ACCOUNT_CODE_DEFINITION_SEQ;

SELECT &1 FROM DUAL;

In this case the &1 refers to the first command line argument.

The Oracle doco is here:http://www.oracle.com/technology/support/tech/sql_plus/htdocs/sub_var9.html

It looks like for our uses '&' and '&&' are equivalent. And any '..' would be converted to a '.'. But a single '.' is just concat.

Jon,

a few remarks before trying to fix this:
Are you aware that both statements should be a line within an sql-file?
If it's inside the pom, there's no reason to interpolate it different than $

: Maven is the only one executing these statements, so use it's power!

DROP SEQUENCE &&schema..ACCOUNT_CODE_DEFINITION_SEQ;

This means you need to have a property called schema.
It's a value in the <properties>-section of the pom, profile or other valid place. Or it's something you add to your Maven-execution like

mvn sql:execute -Dschema=SOME_SCHEMA

SELECT &1 FROM DUAL;

This won't work, we're not executing sqlplus from command-line. In this case you should use the

instead.

If Maven were the only one executing these statements I'd be done. But I have to be able to give the scripts to a customer's DBA and let him execute them using whatever tool he wants.

SELECT &1 FROM DUAL;

Would work if there was some kind of positional substitution available.

The issue db-vendor specific.
I would first use a groovy-script executed by the gmaven-plugin to adjust the sql, next use this plugin to execute the new SQL-files.