You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, we can only support one of each handler type - but what if you have two postgres databases in completely different places?
Let's find some way to dynamically instantiate one handler per connstring. For example, we could move the connstring parser out of the mixin, and then instantiate the handler with a factory method where we pass in the connstring. This would probably be tidier and less magical, anyway.
The text was updated successfully, but these errors were encountered:
lemonsaurus
changed the title
Support multiple databases of the same kind
Support multiple handlers of the same kind
Jan 7, 2021
Right now, we can only support one of each handler type - but what if you have two postgres databases in completely different places?
Let's find some way to dynamically instantiate one handler per connstring. For example, we could move the connstring parser out of the mixin, and then instantiate the handler with a factory method where we pass in the connstring. This would probably be tidier and less magical, anyway.
The text was updated successfully, but these errors were encountered: