I spent all the day on this problem and I've just finally found a solution:
with options(digits=13), it now works.
If I hadn't found this, I would have used the solution of Renaud (but not
very convenient to me).
Nice end of day,
(Happy) Ptit Bleu.
--
View this message in context:
http://r.789
In fact, I always use a string for ID variables because you can get
some funky matching errors due to mismatches in precision.
Bill Gould at Stata Corp said this well in a recent blog post
"1. Use theory to check IDs if they are numeric
One way the id variable can become corrupted is if it is not
Why don't you read/write this field as a character string? Pretty common for
codes.
2011/7/27 PtitBleu
> I've just tested with 12 figures instead of 13. And it works ...
> But I'm not able to modify these numbers as they are codes given by other
> guys (and women as well) to distinguish equipmen
I've just tested with 12 figures instead of 13. And it works ...
But I'm not able to modify these numbers as they are codes given by other
guys (and women as well) to distinguish equipments.
And I thought the limit with R was 15 digits and not 13.
Is it a (bad for me) special feature of the sqlSa
Hello,
After a (bad) first try some months ago, I'm trying again to use RODBC
package instead of DBI+RMySQL packages to populate MySQL database.
The main command is
sqlSave(channel, data_df, tablename, append=T, rownames=FALSE,
colnames=FALSE, fast=FALSE, varTypes=vartypes)
where data_df is the
5 matches
Mail list logo
