[
https://jira.codehaus.org/browse/MSQL-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSQL-56.
------------------------------
Resolution: Won't Fix
The patch contains db-vendor specific and so is the issue.
I would first use a groovy-script executed by the
[gmaven-plugin|http://docs.codehaus.org/display/GMAVEN/Executing+Groovy+Code]
to adjust the sql, next use this plugin to execute the new SQL-files.
> Plugin compatibility with SQLPlus
> ---------------------------------
>
> Key: MSQL-56
> URL: https://jira.codehaus.org/browse/MSQL-56
> Project: Maven 2.x SQL Plugin
> Issue Type: New Feature
> Affects Versions: 1.4
> Environment: Oracle 10
> Reporter: Nick Sayer
> Priority: Minor
> Attachments: msql-56-include.diff
>
>
> We'd like to use the same schema script files operationally to deploy our
> app(s) and for developers to develop with them.
> The issue is that operations uses sqlplus to run the scripts and we'd like
> for the developers to be able to use the sql plugin.
> The problems are twofold (that we've found so far):
> @ include file syntax
> PL/SQL block syntax
> An example of the latter is
> create table bar(insert_ts timestamp not null);
> create or replace trigger foo
> before insert on bar
> for each row
> begin
> select systime into :new.insert_ts FROM DUAL;
> end;
> /
> Note that the create table operation uses ; as the separator / terminator,
> but the trigger uses a / on a line by itself.
> If we use delimitor / and delimitorType row, then the file needs to be
> create table bar(insert_ts timestamp not null)
> /
> create or replace.......
> which, I believe, won't work with sqlplus.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
