[
https://issues.apache.org/jira/browse/TORQUE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534614
]
Thomas Fischer commented on TORQUE-104:
---------------------------------------
I have removed the "comment on ..." stuff from generated sql for sybase. Can
you please get the new templates from svn and check that these templates work
(I cannot check myself, I do not have sybase running)
Please confirm that I have understood the ";" correctly:
Torque's sqlExec executes the script correctly, however it cannot be fed into
the sybase console directly as the sybase console does not like the ";".
Is this correct ?
If yes, how does the sybase console tell that a command ends and a new command
starts ? Is there a "go" after each statement ?
The problem with removing the semicolons is that the sqlExec task needs to know
when a command ends and when the next command begins. The semicolon is used for
this now, and we would need a replacement. Maybe the "go" statement can serve
as such.
> Sybase DBMS DDL errors
> ----------------------
>
> Key: TORQUE-104
> URL: https://issues.apache.org/jira/browse/TORQUE-104
> Project: Torque
> Issue Type: Bug
> Components: Generator
> Affects Versions: 3.3-RC2
> Environment: machine on Windows XP - used Sybase 15.0.2 Developer
> Edition, Maven 2.07 and plugin 3.3-RC2
> Reporter: Sylvain Benoist
> Priority: Blocker
>
> used goals torque:sql ; torque:sqlExec
> When the *-schema.xml file contains descriptions on tables and/or columns,
> the torque:sql goal generates a DDL that contains instructions like
> 'COMMENT ON TABLE blahblahblah IS 'some description' or 'COMMENT ON COLUMN
> blahblah IS...
> Sybase does not support these, so they should be suppressed from the output
> when Sybase is the target database.
> Another issue - Sybase does not like ';' in the DDL -- all it wants to see is
> LF/CR, and 'go' statements
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]