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

Multiple independent connections #43

Closed
wnortje opened this issue Oct 22, 2015 · 2 comments
Closed

Multiple independent connections #43

wnortje opened this issue Oct 22, 2015 · 2 comments

Comments

@wnortje
Copy link
Contributor

wnortje commented Oct 22, 2015

It would be useful if you could open connections to different databases independently. A use case is where a database is selected or created based on information obtained from another database. The current setup in Crane where all db's must be known and defined before making a connection is limiting for this case.

@eudoxia0
Copy link
Owner

eudoxia0 commented Nov 1, 2015

Yes, the current way configuration is handled is a pain. Databases can't be defined dynamically.

@eudoxia0 eudoxia0 added this to the Crane v1.0 milestone Jan 7, 2016
@eudoxia0
Copy link
Owner

eudoxia0 commented Jan 7, 2016

Closing this to just have #12 as the main issue for this.

@eudoxia0 eudoxia0 closed this as completed Jan 7, 2016
@eudoxia0 eudoxia0 self-assigned this Jan 7, 2016
eudoxia0 added a commit that referenced this issue Jan 8, 2016
Sessions associate tables to databases, allowing both multiple concurrent connections and for table definitions to be decoupled from database definitions. This was one of the biggest problems with Crane 0.X, see #12, #43.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants