-
Notifications
You must be signed in to change notification settings - Fork 40
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
Validate dbConnect() parameters #4
Comments
Comment by peternowee The first part of this issue is a duplicate of #55. With regard to the second part:
This seems to be Rcpp complaining about the Current stable (RMySQL 0.10.6) also requires an integer, though it
|
Comment by krlmlr Can we close this? |
Comment by peternowee I think the main point left open here is that parameters of Perhaps this issue could be retitled to something like "dbConnect() parameters should be validated". |
Comment by krlmlr I don't see a reason why a string that looks like an integer shouldn't be coerced to an integer. Other than that, I think the errors emitted by the MySQL driver should be fine in most cases. |
@stevenpollack @peternowee: Coercing to integer now. |
That's the best, thanks! |
- Improve documentation for location of option files, with reference (#18). - Fully support parametrized queries (#22, #27, #39). - Use snake_case in C++ code. - Make transactions compliant to the spec (#38, #49). - 64-bit integers are now supported through the `bit64` package. Unfortunately, this also means that numeric literals (as in `SELECT 1`) are returned as 64-bit integers (#12). - Support timestamp values with sub-second precision on output. - The connection now uses the "utf8mb4" charset by default (#7). - The `port` and `client.flag` arguments to `dbConnect()` are coerced to integer (#4). - Date values with the year beyond 2038 are supported (#56). - Improve DBI compliance (#1, #5, #10, #15, #17, #40). - Correct handling of DATETIME and TIME columns (#52, @noahwilliamsson).
It keep showing me it Help!! |
@thayzacoelho I think that is a different issue. Perhaps #134 or open a new issue. |
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. |
Issue by stevenpollack
Wednesday Mar 11, 2015 at 21:31 GMT
Originally opened as r-dbi/RMySQL#56
Same setup as with issue #55 except my
~/.my.cnf
now is a bit more complicated:and now when I reference the
mysql
group indbConnect
:I know the
~/.my.cnf
is proper, since I can callmysql
and perform queries without issues:Furthermore, when I try to fully qualify my call to
dbConnect
, I get an even weirder error, "Error: not compatible with requested type":The text was updated successfully, but these errors were encountered: