[jira] [Resolved] (EMPIREDB-123) Provide mechanism to distiguish between Unicode and Non-Unicode varchar and char columns in DDL generation

["Rainer Döbele (Resolved JIRA)" <em...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/EMPIREDB-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer Döbele resolved EMPIREDB-123.
------------------------------------

    Resolution: Fixed

Resolved with new column attributed called "singleByteChars".
Use 
   DBTableColumn.setAttribute(DBCOLATTR_SINGLEBYTECHARS, Boolean.TRUE);
and 
   DBTableColumn.isSingleByteChars()


                
> 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.2.1
>            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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira