You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Venkat Ranganathan (JIRA)" <ji...@apache.org> on 2013/03/04 20:21:13 UTC
[jira] [Updated] (SQOOP-928) PostgresqlManager should rollback any
pending changes instead of commit when closing connections
[ https://issues.apache.org/jira/browse/SQOOP-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkat Ranganathan updated SQOOP-928:
-------------------------------------
Attachment: SQOOP-928.patch
Patch with one line fix
> PostgresqlManager should rollback any pending changes instead of commit when closing connections
> ------------------------------------------------------------------------------------------------
>
> Key: SQOOP-928
> URL: https://issues.apache.org/jira/browse/SQOOP-928
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.2
> Environment: Postgresql DB
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Minor
> Attachments: SQOOP-928.patch
>
>
> While closing the connection acquired with getConnection, Postgresql Manager implementation commits any pending changes instead of rolling back.
> If autocommit is off, then the "users" of the connection should commit any persistent changes and not depend on close() calling commit.
--
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