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

Sqlalchemy #240

Merged
merged 118 commits into from
Feb 21, 2022
Merged

Sqlalchemy #240

merged 118 commits into from
Feb 21, 2022

Conversation

nickeopti
Copy link
Contributor

@nickeopti nickeopti commented Dec 2, 2021

Draft, WIP, PR. Just made to keep track of things, and for the tests to run. Can be ignored for now.

Edit: PR for improving the structure and codebase of the drivers. Was originally just for replacing the database specific code with a more general SQLAlchemy implementation. But has now also turned into a bigger, more general refactor of the entire driver code.

@nickeopti nickeopti marked this pull request as ready for review December 2, 2021 13:33
@nickeopti nickeopti marked this pull request as draft December 2, 2021 13:34
@nickeopti nickeopti marked this pull request as ready for review December 2, 2021 13:37
@nickeopti nickeopti marked this pull request as draft December 3, 2021 07:21
@dionhaefner dionhaefner mentioned this pull request Feb 21, 2022
@dionhaefner
Copy link
Collaborator

@nickeopti we good to go?

setup.py Show resolved Hide resolved
@nickeopti
Copy link
Contributor Author

Yes, I believe this is mergeable!

@nickeopti nickeopti merged commit 7011a23 into main Feb 21, 2022
@dionhaefner dionhaefner deleted the sqlalchemy branch February 21, 2022 20:07
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.

Internal reliance on physical order of DB rows Use SQLAlchemy for SQL drivers?
3 participants