search for: writet

...te.table with over 2,147,483,648 elements (C's int limit). I found this bug already reported about before: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. However, there appears to be no solution or fixes in upcoming R version releases. > > The error message is coming from the writetable part of the utils package in the io.c source code(https://svn.r-project.org/R/trunk/src/library/utils/src/io.c): > /* quick integrity check */ > if(XLENGTH(x) != (R_len_t)nr * nc) > error(_("corrupt matrix -- dims not not match length"));...

...this bug already >>> reported about before: >>> https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. However, >>> there appears to be no solution or fixes in upcoming R version >>> releases. >>> >>> The error message is coming from the writetable part of the utils >>> package in the io.c source >>> code(https://svn.r-project.org/R/trunk/src/library/utils/src/io.c): >>> /* quick integrity check */ >>> ???????????????? if(XLENGTH(x) != (R_len_t)nr * nc) >>> ???????????????????? error(_("...

...y 1 TRUE FALSE 2 FALSE TRUE # as promised, the two data frame columns are identified as logicals and # the field types are set to tinyint > field.types <- sapply(a, dbDataType, dbObj = con) > field.types x y "tinyint" "tinyint" # However, in WriteTable, nothing is done to convert the logicals to 0s and 1s. # And logically, the infile is written in TRUE and FALSE and finally, in MySQL # all becomes zero. Here is what we get in MySQL: # row_names x y # 1 0 0 # 2 0 0 # # So, logically this is what we get back in R: > dbWriteTable(c...

...er 2,147,483,648 elements (C's > int limit). I found this bug already reported about before: https://bugs.r- > project.org/bugzilla/show_bug.cgi?id=17182. However, there appears to be no > solution or fixes in upcoming R version releases. > > The error message is coming from the writetable part of the utils package > in the io.c source code(https://svn.r- > project.org/R/trunk/src/library/utils/src/io.c): > /* quick integrity check */ > if(XLENGTH(x) != (R_len_t)nr * nc) > error(_("corrupt matrix -- dims not not match > l...

...csv or write.table with over 2,147,483,648 elements (C's int limit). I found this bug already reported about before: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. However, there appears to be no solution or fixes in upcoming R version releases. The error message is coming from the writetable part of the utils package in the io.c source code(https://svn.r-project.org/R/trunk/src/library/utils/src/io.c): /* quick integrity check */ if(XLENGTH(x) != (R_len_t)nr * nc) error(_("corrupt matrix -- dims not not match length")); The issue is th...

...ents (C's int limit). I found this bug already reported about >> before: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. >> However, there appears to be no solution or fixes in upcoming R >> version releases. >> >> The error message is coming from the writetable part of the utils >> package in the io.c source >> code(https://svn.r-project.org/R/trunk/src/library/utils/src/io.c): >> /* quick integrity check */ >> ???????????????? if(XLENGTH(x) != (R_len_t)nr * nc) >> ???????????????????? error(_("corrupt matrix -- di...

...t;>> reported about before: >>>> https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. However, >>>> there appears to be no solution or fixes in upcoming R version >>>> releases. >>>> >>>> The error message is coming from the writetable part of the utils >>>> package in the io.c source >>>> code(https://svn.r-project.org/R/trunk/src/library/utils/src/io.c): >>>> /* quick integrity check */ >>>> ???????????????? if(XLENGTH(x) != (R_len_t)nr * nc) >>>> ???????????????...

Hi, The problem was the row.names that were sent to the database and created an primary key duplicate. Now it works fine. BTW congratulations for the package. It copied 15300 rows by 11 columns in less than 5 seconds, in my PIII 833 with 1 GB RAM. > system.time(dbWriteTable(con, "TBL_SIMDATA", TBL.SIMDATA, append = TRUE, row.names=F)) [1] 3.87 0.05 4.86 0.01 0.00 Just one suggestion. It would be usefull to have a more verbose output, maybe the "LOAD DATA INFILE" output. Thanks for your help. EJ On Tue, 2004-05-25 at 13:01, Sean Davis wr...