You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2013/02/04 15:16:13 UTC
[jira] [Closed] (EMPIREDB-123) Provide mechanism to distiguish
between Unicode and Non-Unicode varchar and char columns in DDL generation
[ https://issues.apache.org/jira/browse/EMPIREDB-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-123.
----------------------------------
Cleanup of unclosed issues.
> Provide mechanism to distiguish between Unicode and Non-Unicode varchar and char columns in DDL generation
> ----------------------------------------------------------------------------------------------------------
>
> Key: EMPIREDB-123
> URL: https://issues.apache.org/jira/browse/EMPIREDB-123
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-2.3.0
> Reporter: Rainer Döbele
> Assignee: Rainer Döbele
>
> Currently for DBMS that support Unicode and non-unicode like SQL Server and Oracle text (varchar) and char columns are created as Unicode columns by default. If non-unicode columns are desired, there is currently an undocumented way by setting a negative length.
> However this meachnism is intransparent and error-prone.
> Hence this feature should be solved by defining a specific column attribute that deals with this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira