[
https://issues.apache.org/jira/browse/SQOOP-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335922#comment-14335922
]
ASF subversion and git services commented on SQOOP-2130:
--------------------------------------------------------
Commit 653668f0f6c74225c66e100989717a5152253188 in sqoop's branch
refs/heads/trunk from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=653668f ]
SQOOP-2130: BaseSqoopTestCase should use manager.escapeTable instead of
directly hardcoding double quotes
(Jarek Jarcec Cecho via Abraham Elmahrek)
> BaseSqoopTestCase should use manager.escapeTable instead of directly
> hardcoding double quotes
> ---------------------------------------------------------------------------------------------
>
> Key: SQOOP-2130
> URL: https://issues.apache.org/jira/browse/SQOOP-2130
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.6
>
> Attachments: SQOOP-2130.patch
>
>
> I've changed {{BaseSqoopTestCase}} in SQOOP-1890 to hardcode escape character
> for table name to be double quotes per ANSI standard. Sadly this won't work
> with default MySQL configuration and breaks unless the server administrator
> sets {{sql_mode}} to {{ANSI_QUOTES}}. This seems unnecessary, so I would like
> to fix Sqoop instead to use the proper encoding character.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
