[
https://issues.apache.org/jira/browse/TORQUE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020701#comment-18020701
]
Georg Kallidis commented on TORQUE-373:
---------------------------------------
One simple idea to not have an "exception" would be to predefine the
"hasDefault" with _default_ to true, which means it may be set in the Platform
interface (
{code:java}
default hasDefault(String sqlType) return true
{code}
] and overridden only for longvarchar in mysql (platform).
> DEFAULT value generated for non supporting sql-types
> ----------------------------------------------------
>
> Key: TORQUE-373
> URL: https://issues.apache.org/jira/browse/TORQUE-373
> Project: Torque
> Issue Type: Task
> Components: Templates
> Affects Versions: 6.0, 7.0
> Reporter: Max Philipp Wriedt
> Assignee: Max Philipp Wriedt
> Priority: Major
>
> When defining a column as LONGVARCHAR with a default value the SQL generated
> contains a "DEFAULT" which is invalid for the mapped "MEDIUMTEXT" in
> MySQL/MariaDB. (but might be ignored/warning-only based on the executor of
> the SQL-schema).
> I've started working on a fix, but I'm indifferent, whether this is a special
> case for MySQL or if we should add a "hasDefault" at the Platform interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
