[
https://issues.apache.org/jira/browse/TORQUE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291530#comment-13291530
]
Thomas Fox commented on TORQUE-203:
-----------------------------------
As to printing a warning for reserved words: who reads such warnings hidden in
the output of, e.g., a maven build ? I'd guess in 95 % of all cases such
warnings are not read and therefore not worth the trouble.
Alternatively, there is already a "strict" schema which tries to forbid (some)
things which are not portable across databases.
We could forbid all SQL reserved words as table or column names in the strict
schema.
Do you think this would be an acceptable solution ?
(There is a good listof reserved words e.g. at
http://www.postgresql.org/docs/9.1/static/sql-keywords-appendix.html)
> Quote table names in creation
> -----------------------------
>
> Key: TORQUE-203
> URL: https://issues.apache.org/jira/browse/TORQUE-203
> Project: Torque
> Issue Type: Improvement
> Reporter: Thomas Fox
>
> For some databases, table names can be quoted in the sql create scripts to
> avoid collisions with predefined names. Where possible, such quotation should
> be used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
