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
{{ message }}
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
While I appreciate the attention to detail in the messages about reserved characters needing to be quoted in SQL queries, it would be great if there was an option to suppress these messages (either via an options() setting and/or function argument).
Many R users will use MonetDBLite as a database backend with dplyr / dbplyr, which already automatically quotes reserved characters, making these messages unnecessary and potentially confusing. I'm also using MonetDBLite as a backend in a few packages (for which I have a huge Thank You! being able to access a modern, fast, column-oriented database system that supports windowing functions without any server-side installation is completely game-changing), and would rather hide these messages from users since the quoting is taken care of.
Also wondering if they should be typed as warnings instead of messages? I suppose a case could be made either way.
Anyway, thanks for considering this request, and thanks again for this excellent package. I recently read your arxiv piece which I now send to pretty much everyone.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While I appreciate the attention to detail in the messages about reserved characters needing to be quoted in SQL queries, it would be great if there was an option to suppress these messages (either via an
options()
setting and/or function argument).Many R users will use MonetDBLite as a database backend with
dplyr
/dbplyr
, which already automatically quotes reserved characters, making these messages unnecessary and potentially confusing. I'm also using MonetDBLite as a backend in a few packages (for which I have a huge Thank You! being able to access a modern, fast, column-oriented database system that supports windowing functions without any server-side installation is completely game-changing), and would rather hide these messages from users since the quoting is taken care of.Also wondering if they should be typed as warnings instead of messages? I suppose a case could be made either way.
Anyway, thanks for considering this request, and thanks again for this excellent package. I recently read your arxiv piece which I now send to pretty much everyone.
The text was updated successfully, but these errors were encountered: