You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Joachim Wackerow (JIRA)" <ji...@apache.org> on 2006/03/15 09:23:52 UTC
[jira] Created: (DDLUTILS-80) nativeDefault attribute for column,
which is not interpreted by DdlUtils at all
nativeDefault attribute for column, which is not interpreted by DdlUtils at all
-------------------------------------------------------------------------------
Key: DDLUTILS-80
URL: http://issues.apache.org/jira/browse/DDLUTILS-80
Project: DdlUtils
Type: New Feature
Environment: all
Reporter: Joachim Wackerow
Assigned to: Thomas Dudziak
A column attribute "nativeDefault" would enable a definition of a default value which is not interpreted by DdlUtils at all. The value of the attribute would be the value of the SQL DEFAULT as is.
Example:
<column name="timestamp" type="TIMESTAMP" nativeDefault="CURRENT_TIMESTAMP"/>
would result in SQL code:
ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP
With the existing column attribute default it would result in (which is not desired):
ts TIMESTAMP DEFAULT 'CURRENT_TIMESTAMP'
Comment from Tom:
In general the default value is expected to be a string value that can
be converted to the Java type corresponding to the JDBC type (as
defined by the JDBC spec).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DDLUTILS-80) nativeDefault attribute for column,
which is not interpreted by DdlUtils at all
Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DDLUTILS-80?page=all ]
Thomas Dudziak updated DDLUTILS-80:
-----------------------------------
Fix Version: 1.1
> nativeDefault attribute for column, which is not interpreted by DdlUtils at all
> -------------------------------------------------------------------------------
>
> Key: DDLUTILS-80
> URL: http://issues.apache.org/jira/browse/DDLUTILS-80
> Project: DdlUtils
> Type: New Feature
> Environment: all
> Reporter: Joachim Wackerow
> Assignee: Thomas Dudziak
> Fix For: 1.1
>
> A column attribute "nativeDefault" would enable a definition of a default value which is not interpreted by DdlUtils at all. The value of the attribute would be the value of the SQL DEFAULT as is.
> Example:
> <column name="timestamp" type="TIMESTAMP" nativeDefault="CURRENT_TIMESTAMP"/>
> would result in SQL code:
> ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP
> With the existing column attribute default it would result in (which is not desired):
> ts TIMESTAMP DEFAULT 'CURRENT_TIMESTAMP'
> Comment from Tom:
> In general the default value is expected to be a string value that can
> be converted to the Java type corresponding to the JDBC type (as
> defined by the JDBC spec).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DDLUTILS-80) nativeDefault attribute for column,
which is not interpreted by DdlUtils at all
Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DDLUTILS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Dudziak updated DDLUTILS-80:
-----------------------------------
Fix Version/s: (was: 1.1)
1.2
> nativeDefault attribute for column, which is not interpreted by DdlUtils at all
> -------------------------------------------------------------------------------
>
> Key: DDLUTILS-80
> URL: https://issues.apache.org/jira/browse/DDLUTILS-80
> Project: DdlUtils
> Issue Type: New Feature
> Components: Core (No specific database)
> Environment: all
> Reporter: Joachim Wackerow
> Assignee: Thomas Dudziak
> Fix For: 1.2
>
>
> A column attribute "nativeDefault" would enable a definition of a default value which is not interpreted by DdlUtils at all. The value of the attribute would be the value of the SQL DEFAULT as is.
> Example:
> <column name="timestamp" type="TIMESTAMP" nativeDefault="CURRENT_TIMESTAMP"/>
> would result in SQL code:
> ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP
> With the existing column attribute default it would result in (which is not desired):
> ts TIMESTAMP DEFAULT 'CURRENT_TIMESTAMP'
> Comment from Tom:
> In general the default value is expected to be a string value that can
> be converted to the Java type corresponding to the JDBC type (as
> defined by the JDBC spec).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DDLUTILS-80) nativeDefault attribute for column,
which is not interpreted by DdlUtils at all
Posted by "Thomas Dudziak (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DDLUTILS-80?page=all ]
Thomas Dudziak updated DDLUTILS-80:
-----------------------------------
Component: Core (No specific database)
> nativeDefault attribute for column, which is not interpreted by DdlUtils at all
> -------------------------------------------------------------------------------
>
> Key: DDLUTILS-80
> URL: http://issues.apache.org/jira/browse/DDLUTILS-80
> Project: DdlUtils
> Type: New Feature
> Components: Core (No specific database)
> Environment: all
> Reporter: Joachim Wackerow
> Assignee: Thomas Dudziak
> Fix For: 1.1
>
> A column attribute "nativeDefault" would enable a definition of a default value which is not interpreted by DdlUtils at all. The value of the attribute would be the value of the SQL DEFAULT as is.
> Example:
> <column name="timestamp" type="TIMESTAMP" nativeDefault="CURRENT_TIMESTAMP"/>
> would result in SQL code:
> ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP
> With the existing column attribute default it would result in (which is not desired):
> ts TIMESTAMP DEFAULT 'CURRENT_TIMESTAMP'
> Comment from Tom:
> In general the default value is expected to be a string value that can
> be converted to the Java type corresponding to the JDBC type (as
> defined by the JDBC spec).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira