Matt Hegarty

Closing due to inactivity

I'm not sure this is the right approach to be frank. Catching and re-raising exceptions to be more generic could cause other issues, especially for those not using the UI....

Thanks for submitting this, but I am closing as per [comment](https://github.com/django-import-export/django-import-export/pull/1467#issuecomment-1282579668)

Closing this for now. I'm not keen on rethrowing exceptions as per comment [here](https://github.com/django-import-export/django-import-export/pull/1467#issuecomment-1282579668).

> We can possibly allow both execute and executemany to return the statement result. This would be fantastic. ATM I have to trade off using `conn.execute()` for readability vs `executemany()`...

Just wanted to link the other related thread. You [mention](https://github.com/MagicStack/asyncpg/issues/448#issuecomment-498410079) that you could allow `executemany` to return the statement result, is this on the roadmap?

Basically I had limited success in optimising. Some findings noted [here](https://github.com/izimobil/django-rest-framework-datatables/pull/138#issuecomment-1320902130)

I refactored the documentation in 3.1.0. It would be great to update this issue in the light of those changes.

Also updating documentation significantly in the [`release-4`](https://github.com/django-import-export/django-import-export/tree/release-4) branch.

Documentation has been extensively updated for [`release-4`][1]. I propose to close this and we can open other issues or comment further if extra documentation is required. [1]: https://django-import-export.readthedocs.io/en/4.0.0-beta.1/