similar to: RODBC sqlSave problem with bigint numbers

Dear Tobias, I finally succeeded in exporting my dataframes from R into Access with this script: library(RODBC) canal <- odbcConnectAccess("D:/Floristique.mdb") sqlSave(channel=canal, dat=flore, tablename="Floristique", rownames=F, safer=F, fast=F, varTypes=c(dates="Date")) odbcClose(canal) My problem in exporting my dataframe "flore" seems to

Hello, I contact you after having unsuccessfully asked my question to R mailing list. I use the package RODBC to connect to a MS-SQL server. I am able to getQuery from the database. I am now studying the sqlSave some data into the database. Unfortunetly, I meet some issues relating to the format of the data that arrives into the database. I have three columns. The first one should be in the

Hey everyone, I don't have a question. Instead some helpful advice with things I've learned from trying to connect 'R' to databases using RODBC. ROBDC is a very handy tool that, once you have everything fixed up nicely, is a great way to have scripts run fairly autonomously, safe in the knowledge that data isn't accidentally messed up. But I was fairly ignorant

Hola Javier, si no estoy entendiendo mal, lo q deseo hacer no se trata de configurar los parametros SQL, sino solo de colocar un vector en el argumento VarTypes de la funcion sqlSave. El manual especifica esa opcion, pero no da ningun ejemplo de como usarla. *varTypes an optional named character vector giving the DBMSs datatypes to be used for* *some (or all) of the columns if a table is to be

Buen dia Javier, muchas gracias por tu ayuda y el script compartido. Me va a servir como ayuda para seguir aprendiendo sobre RODBC pero no encuentro una solucion para este problema puntual de poder definir el tipo y ancho de las variables, q segun creo se hace con el argumento varTypes. Si alguien tien algun ejemplo donde haya usado la SqlSave y VarTypes, me sera de gran ayuda. Abrazo a todos

Buen dia compañerxs de R, les traigo una pregunta bastante especifica. En el trabajo me estan requiriendo el uso de SQL, asi q estoy aprendiendo a usarlo desde R, con el paquete RODBC. Mi problema puntual es que al crear una tabla en el servidor SQL a partir de un data frame en R (usando la funcion sqlSave) no puedo definir el tipo de variables que quiero usar en el data frame. Segun entiendo

I am using R2.6.0 on “Windows Small Business Server 2003”. I apologize if the answer to my question is available…I have searched but have not found anything that I thought helped me. I have a dataframe that contains ~4.5 million rows and 5 columns. (see memory and df details below). I am trying to save the dataframe to a MS SQL Server database, using the “sqlSave” function. The code

I am running R version 2.8.1 on Windows XP OS. This works fine. (Data.frame dta is created with records from the DB2 table.): sql <- "select * from storage.testappend_slt order by uut" dta <- sqlQuery(channel,sql) But when I try to append records (from data.frame newdta) to the same DB2 table. I get an error: sqlSave(channel, newdta, tablename = storage.testappend_slt, append

Hello, I'm still trying to modify my script in order to use RODBC instead of RMySQL (no more ready-to-use package for windows). My new problem is the following one (not seen with RMySQL): I'd like to copy a data.frame to a mysql table. One column is a numeric one with big integer like : 2005000206110 (13 figures) If I type this number in R, I get: 2.005e+12 and when I use sqlSave to

Till yesterday I was more than satisfied by RODBC, specifically by sqlSave which I had been happily using in a daily crontab R batch job regularly updating a postgresql db for as long as one year. In this R- batch I was able to save records into indexed tables *** even though *** they already existed. in this case sqlSave simply neglected those rows of the input table that were offending the

hi, just wondering do migration support MySQL BIGINT ? what if i wanna create a migration with BIGINT ? should i use SQL directly ? kiwi -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hi - I have a simple R script that inserts values into a Postgres table to generate a record that autogenerates a bigint unique ID (basically, a customized bigserial value). When I query the table to retrieve the bigint value, the value returned is not the same as the value created in the database (as evidenced by a direct query of the database table via pgAdmin). e.g. the value created should

Hi, I am having trouble to write/create a table, which has a date field. I want to create a stock price table, which has fields of ticker, date, price. First, I created such a table in Microsoft Access with a few rows inputs. Using sqlQuery, I found that the date field was retrieved as POSIXct value. Then I made a data.frame with POSIXct as the data type for dates. However, I received the

I have to create Migration file form Mysql DB But I want type of Migration equivalent with Mysql DB (example : in Mysql with type Bigint and in Migration will have type Int(20) or Bigint) Could You help me solve this Problem? Thanks -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To

Dear Group, if anyone has experience with the RMySQL Package maybe this behaviour is know: Reading data from a table into R the fields with datatype bigint(20) unsigned are transformed in some way: e.g. the query "select * from orders where userid = 14929859848712890325" selects the correct case but in R the userid is changed to 14929859848712890368. What happened here? This

I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt. Is the only solution to uninstall the base version and then install the rpmforge version? According the the wiki "Packages from repositories with a lower priority will never be used to upgrade

Hi, Is there a way to tell to the migrations to use bigint(20) instead of int(11) for ids? Thanks, Fuad. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060227/0896c124/attachment.html

The MySQL/Ruby library doesn''t properly handle inserts into tables with the primary key being a BIGINT If the ID returned to the MySQL/Ruby library is LARGER than the INT range, the value is returned to Ruby truncated and incorrect. This is then passed up to ActiveRecord and into the id field of your model. The actual INSERT worked properly and when do you an ActiveRecord find for the

I had to move a perl script from an old server to a new one. Both the old and new servers are running "CentOS release 5.10 (Final)" and perl v5.8.8. (But the problem I'm running into appears to be a package management problem and not a Perl problem which is why I'm posting it to a CentOS list.) The line of code in the script that attempts to open a Net::SFTP connection,

I am using sqlSave to save my data into an existing table at MS SQL Server database. Previously my code ran smoothly but all of a sudden it stopped working. Here is my code: sqlSave(con, highVol, "dbo.futuresHighVol", append=TRUE, rownames=FALSE) Error: sqlSave(con, highVol, "jrgchis.dbo.futuresHighVol", append = TRUE, : 42S01 2714 [Microsoft][ODBC SQL Server Driver][SQL