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.

Sign up for GitHub

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

Jump to bottom

Consistent strategy for connection cloning #22

Closed
hadley opened this issue Oct 31, 2013 · 2 comments
Closed

Consistent strategy for connection cloning #22

hadley opened this issue Oct 31, 2013 · 2 comments

Comments

@hadley
Copy link
Member

hadley commented Oct 31, 2013

If length(dbListResults(con)) > 0, functions:

  • clone silently (e.g. sqliteTableFields)
  • throws an error (e.g. sqliteTransactionStatement)
  • do nothing (the majority)

We need a clearly articulated strategy to adhere to.
@hadley
Copy link
Member Author

hadley commented Sep 4, 2014

Connection cloning is dangerous because cloning an in-memory on temporary on disk file creates a new temporary database, not what the user will expect!

@hadley hadley closed this as completed in ebfccf8 Sep 4, 2014
@github-actions
Copy link

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hadley