[
https://issues.apache.org/jira/browse/SQOOP-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096349#comment-14096349
]
ASF subversion and git services commented on SQOOP-1429:
--------------------------------------------------------
Commit 74ec89452b574f29fb0ef3615c18184c86a559cc in sqoop's branch
refs/heads/trunk from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=74ec894 ]
SQOOP-1429: Fix native characters usage for SqlServer object names
(Venkat Ranganathan via Jarek Jarcec Cecho)
> Fix native characters usage for SqlServer object names
> ------------------------------------------------------
>
> Key: SQOOP-1429
> URL: https://issues.apache.org/jira/browse/SQOOP-1429
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/sqlserver
> Affects Versions: 1.4.5
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Fix For: 1.4.6
>
> Attachments: SQOOP-1429.patch
>
>
> While SQOOP-1412 introduced NCHAR/NVARCHAR columns to be splittable, there
> are a couple of other issues with characters in non-default collation.
> The metadata queries where not using N prefix in the metadata queries
> involving tablenames with native character set (not part of the default
> collation)
> Also update the NCHAR/NVARCHAR splitter to use the N'..' prefix for the
> string constants generated in the split sql
--
This message was sent by Atlassian JIRA
(v6.2#6252)
