Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A dirty fix for #399, does not account for other possible rollbacks #689

Closed
wants to merge 1 commit into from

Conversation

int-ua
Copy link
Contributor

@int-ua int-ua commented Nov 29, 2017

Sorry, no time for a proper patch, feel free to reject it and create a better one, just posting here as a possible workaround until a better patch is made.

@coveralls
Copy link

coveralls commented Nov 29, 2017

Coverage Status

Coverage increased (+0.007%) to 90.626% when pulling 0b31810 on int-ua:399-dirty into af35835 on django-import-export:master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.007%) to 90.626% when pulling 0b31810 on int-ua:399-dirty into af35835 on django-import-export:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.007%) to 90.626% when pulling 0b31810 on int-ua:399-dirty into af35835 on django-import-export:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.007%) to 90.626% when pulling 0b31810 on int-ua:399-dirty into af35835 on django-import-export:master.

@manelclos
Copy link
Contributor

Thanks @int-ua, this is going to change in the new transaction management, see #690

@bmihelac
Copy link
Member

resolved with 9a32c6e, @int-ua thanks for reporting, testing and initial patch

@bmihelac bmihelac closed this Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants