[
http://jira.codehaus.org/browse/MSQL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSQL-39.
------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Assignee: Robert Scholte
Resolved by fix of MSQL-47
> /* */ comments in SQL containing semicolons are not supported except in block
> mode
> ----------------------------------------------------------------------------------
>
> Key: MSQL-39
> URL: http://jira.codehaus.org/browse/MSQL-39
> Project: Maven 2.x SQL Plugin
> Issue Type: Bug
> Affects Versions: 1.0, 1.3
> Environment: Oracle DB
> Reporter: Bryan Loofbourrow
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 1.4
>
>
> If you have a comment in the sql file that you're trying to execute, like
> /* Modified in Apr-2009; added index */
> You will get an Oracle error trying to execute. The reason is that
> SqlExecMojo does not parse for /* */ comments; it assumes that anything
> starting from the beginning of the file, or the end of a prior statement, and
> ending with a semicolon, is a SQL statement that it should send to the
> database. If there's a semicolon in a /* */ comment, as above, it will send
> the first part of the comment, through the semicolon, to the database, and
> the database will send back an error.
> Semicolons in a /* */ block should not be treated as end-of-statement.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
