# Comparing different methods of rolling back database changes in pytest tests for SQLAlchemy

**URL:** <https://discuss.elastic.co/t/comparing-different-methods-of-rolling-back-database-changes-in-pytest-tests-for-sqlalchemy/364354>\
**Category:** Kibana\
**Tags:** elastic-stack-sql\
**Created:** [August 5, 2024, 7:49am UTC](https://discuss.elastic.co/t/comparing-different-methods-of-rolling-back-database-changes-in-pytest-tests-for-sqlalchemy/364354 "2024-08-05T07:49:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivan/32/136062_2.png) [@vivan](https://discuss.elastic.co/u/vivan)\
**Post date:** [August 5, 2024, 7:49am UTC](https://discuss.elastic.co/t/comparing-different-methods-of-rolling-back-database-changes-in-pytest-tests-for-sqlalchemy/364354/1 "2024-08-05T07:49:39Z")

</div>

I'm working on a project that uses FastAPI and [SQL](https://hkrtrainings.com/postgresql-training) Alchemy asynchronously.  
I've written pytest tests for this project and have successfully implemented database rollback after each test run.  
I've found two different implementation methods, but I'm unsure about the differences between them. Are both methods correct, or is one potentially problematic?

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [August 6, 2024, 7:51pm UTC](https://discuss.elastic.co/t/comparing-different-methods-of-rolling-back-database-changes-in-pytest-tests-for-sqlalchemy/364354/2 "2024-08-06T19:51:37Z")

</div>

Thanks for reaching out. Can you provide some more context about the problem you are facing? Is this an Elastic issue?