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

Can't have multiple simultaneous in-memory MonetDB farms active #5

Open
gijzelaerr opened this issue May 14, 2020 · 3 comments
Open
Assignees
Milestone

Comments

@gijzelaerr
Copy link
Collaborator

We solve this now by switching context, but we run into issues in case of multiple in memory farms, our context switcher will return the same instance.

@gijzelaerr gijzelaerr self-assigned this May 14, 2020
@gijzelaerr
Copy link
Collaborator Author

I now realise that I've been using the path as a context identifier, but maybe I should use the owning python connection as an identifier.

@gijzelaerr gijzelaerr added this to the 0.5 milestone May 14, 2020
@ghost
Copy link

ghost commented May 22, 2020

No, currently there are too many global variables to allow for multiple embedded (!) database connections to be open at the same time.
However, it is conceivable that you open a remote connection an using
rm = monetdbe.open(database='myremote', user=...., host='someip', port=5000)
and a
mm = monetdbe.open(':in-memory')

This way there can be at most one (1) in-memory database open

@gijzelaerr gijzelaerr modified the milestones: 0.5, 0.6, 1.0 May 22, 2020
@gijzelaerr gijzelaerr modified the milestones: 1.0, 0.7 Jun 17, 2020
@gijzelaerr
Copy link
Collaborator Author

todo gijs: raise exception on double memory database

@gijzelaerr gijzelaerr changed the title Can't have multiple simultaneous MonetDB farms active Can't have multiple simultaneous in-memory MonetDB farms active Jun 17, 2020
@gijzelaerr gijzelaerr modified the milestones: 0.7, 0.8 Jun 17, 2020
gijzelaerr added a commit that referenced this issue Jun 17, 2020
@gijzelaerr gijzelaerr modified the milestones: 0.8, 0.9 Jun 30, 2020
@gijzelaerr gijzelaerr modified the milestones: 0.9, 0.10 Sep 11, 2020
@gijzelaerr gijzelaerr modified the milestones: 0.10, 0.11 Apr 30, 2021
@gijzelaerr gijzelaerr modified the milestones: 0.11, 1.0 Jun 9, 2021
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

No branches or pull requests

1 participant