[jira] [Updated] (TORQUE-373) DEFAULT value generated for non supporting sql-types
"Max Philipp Wriedt (Jira)" <[email protected]> Mon, 15 Sep 2025 08:22:00 +0000 (UTC)
| Newsgroups | gmane.comp.jakarta.turbine.torque.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/TORQUE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Philipp Wriedt updated TORQUE-373:
--------------------------------------
Summary: DEFAULT value generated for non supporting sql-types (was: DEFAULT value generated for non suppurted sql-types)
> 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)