-
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
dbWriteTable ignores field.types param #10
Comments
Comment by pantoniades Sorry, to be more exact it was that in the dbWriteTable(MySQL(), character, data.frame) form it only passes in the df to the sqlCreateTable() call, so column types are determined regardless of what's in the field.types parameter. |
Comment by jlsepulveda Hi pantoniades I have the same behaviour using dbWriteTable, do you have any update related? Thanks |
Comment by pantoniades Hi, I fixed it in my own branch - see Philip |
- 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).
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 pantoniades
Thursday Apr 23, 2015 at 16:33 GMT
Originally opened as r-dbi/RMySQL#67
Passing in a list of field types has no effect on dbWriteTable.
It appears to be that they do not get passed in to the call to DBI::sqlCreateTable on line 92 of table.R
It's a small change, and I am happy to send a pull request.
thanks
The text was updated successfully, but these errors were encountered: