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

Automatically initialise extensions #236

Closed
hadley opened this issue Oct 23, 2017 · 3 comments
Closed

Automatically initialise extensions #236

hadley opened this issue Oct 23, 2017 · 3 comments

Comments

@hadley
Copy link
Member

hadley commented Oct 23, 2017

There doesn't seem to be any harm to this. If necessary, could include an argument in dbConnect method allowing you to suppress it if you really wanted.

@krlmlr
Copy link
Member

krlmlr commented Dec 9, 2017

We already have the loadable.extensions argument to dbConnect(), if it's FALSE then initExtension() fails. Do we need another argument?

@hadley
Copy link
Member Author

hadley commented Dec 10, 2017

Yeah that'd be great - maybe default.extensions = TRUE?

@krlmlr krlmlr closed this as completed in 020a009 Mar 23, 2018
krlmlr added a commit that referenced this issue Mar 25, 2018
- Values of class `"integer64"` are now supported for `dbWriteTable()` and `dbBind()` (#243).
- New connections now automatically load default RSQLite extensions (#236).
- Implement `dbUnquoteIdentifier()`.
- Update bundled sqlite3 library to 3.22 (#252).
- Names in the `x` argument to `dbQuoteIdentifier()` are preserved in the output (r-lib/DBI#173).
- Fix rchk warnings on CRAN (#250).
- `dbRowsAffected()` and `dbExecute()` return zero after a `DROP TABLE` statement, and not the number of rows affected by the last `INSERT`, `UPDATE`, or `DELETE` (#238).
- Refactor connection and result handling to be more similar to other backends.
- Fix `dbQuoteIdentifier()` to ignore invalid UTF-8 strings (r-dbi/DBItest#156).
@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2020

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 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants