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 database error prevents all future database interactions from working #263

Closed
turt2live opened this issue Jan 9, 2019 · 1 comment
Closed
Labels
bug: defect Something isn't working and it never has worked
Milestone

Comments

@turt2live
Copy link
Contributor

if there's something like "duplicate key for table portals" the bridge should still work for every other interaction with the database.

If this the database error is unrecoverable, prefer crashing.

@tulir tulir added the bug: defect Something isn't working and it never has worked label Feb 11, 2019
@tulir
Copy link
Member

tulir commented Feb 11, 2019

I'm going to reduce ORM usage which should make it be less stuck after a failing transaction. It should also be easier to avoid invalid transactions with SQLAlchemy Core since there I can actually see what I'm doing in the database.

@tulir tulir added this to the 0.5.0 milestone Feb 11, 2019
@tulir tulir closed this as completed in c2172aa Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: defect Something isn't working and it never has worked
Development

No branches or pull requests

2 participants