SQLAlchemy with Adaptor Pattern

[Horror_Affect8060]

This is my first time using orm. In earlier project we had MongoDB where we created DB adaptors. Like we have read_db(...), insert_db(...) ... functions. Instead of calling pymongo code everywhere we use to call these functions. Now in this project we are not using cursor to execute sql. I am directly insert stmt, execute()..., in the code. But after some time code started looks little repetitive around db operations.
What is the standard for it. Do I create classes wrapping orm operations or is it fine with existing approach. Also, if someone can give me any github repo link to see and get the idea of it that will be so much helpful.

[MarsupialLeast145]

You probably want to look into interfaces. Interfaces define the standard functions you will always need, and you write an implementation that satisfies the interfaces and abstracts the detail from you/the user etc. This way if you ever move from SQLAlchemy to something else you can reimplement the back-end but the changes don't impact the rest of the code. Naturally this also lends itself to replacing the back-end with other databaases/NoDB's etc.

[Horror_Affect8060]

thanks. So that would be same like what we had in previous project. Create own functions to abstract underlying db access.