Displaying 20 results from an estimated 1000 matches similar to: "sqlSave reports invalid regular expression '[^[:alnum]_]+' (PR#7704)"
2005 Feb 24
2
sqlSave reports invalid regular expression '[^[:alnum]_]+' (PR#7703)
Full_Name: David Whiting
Version: 2.1.0 Under development (unstable)
OS: linux
Submission from: (NULL) (82.39.106.169)
I have just upgraded from a previous version (2.0.0?) and found some of my code
that used okay to run now gives an error. The function being called is
sqlSave(). I am pretty sure (but not 100% certain) that the data frame I am
trying to save has not changed. I am 100% sure that
2000 Mar 08
0
RODBC: follow up
Hi Michael,
Here is the result of my first testing:
(0) Dr. Watson
Sorry, I should have given a more precise description: by default in R
exists a function with the name 'table', if you use this name as in
odbcPrimaryKeys(0, table)
a Dr. Watson occurs, because table does not give a table name.
However, it is always a good idea to prevent Dr. Watsons, even if it is
triggered by a
2008 May 07
0
RODBC sqlSave with multiple schema in DB2
Hi,
I am trying to use sqlSave to write a dataframe to an existing table in a
DB2 database. The database contains two schemas. My experience is the
following: (1) in the case that tablename is left empty in sqlSave, R
writes to the instance level schema (2) in the case that a tablename is
specified and that table name exists only once in the database, R will
write to that table irrespective
2006 Mar 23
0
sqlSave
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
2007 Feb 02
0
New RODBC: a problem with sqlSave
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
2010 May 20
0
RODBC: sqlSave leave primary key and other columns null
I have an existing table, and I am trying to use sqlSave to append
additional rows to this database. I omit the primary key, which is a
uniqueidentifier type (MS SQL), so that the database can populate that
field. However, I get the following error:
> sqlSave( ch, result, tablename=thetablename, append=TRUE,
rownames=FALSE, colnames=FALSE )
Error in odbcUpdate(channel, query, mydata,
2006 Dec 22
1
bug in sqlSave with fast=F option (PR#9429)
Full_Name: Paul MacManus
Version: 2.3.0
OS: Windows XP
Submission from: (NULL) (216.90.169.253)
See also R-help thread for October 18, 2006
---------------------------
Create a dataframe and save it to a database table "test" as follows:
df <- data.frame(T=1, S=10)
sqlSave(channel, df, "test", rownames=F)
The table now looks like
T S
1 10
If I create another
2011 Nov 10
1
Help: sqlSave Error
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
2006 Oct 18
2
sqlSave, fast=F option, bug?
Hi,
Using the fast=F option, sqlSave saves without matching column names.
It looks like a bug to me..........
Here's a simple (artificial) example.
-----------------------------------------
Create a dataframe and save it to a database table "test" as follows:
df <- data.frame(T=1, S=10)
sqlSave(channel, df, "test", rownames=F)
The table now looks like
T S
1 10
If
2007 Oct 22
0
RODBC problem: sqlSave not working after an update
Good day, all.
I just upgraded to R 2.6.0. I re-installed my most-used packages including RODBC to be sure I'm up-to-date. I have been working with a large insurance claims dataset stored in a MS-Access database on a Windows machine. I have been regularly exporting tables from R into it using sqlSave. It's worked like a charm until today, when this happened:
>
2009 Jul 08
0
RODBC and sqlSave issue
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
2003 Jan 29
1
RODBC sqlSave Error
Hi,
i get error after using a data.frame with subset for "sqlSave".
What can i do ?
It seems that lines like this in a data.frame structure are after subset
deleted and cause
the error ?
- attr(*, "variable.labels")= Named chr "CUSID" "Welle"
"Arbeitgeberfavorit1" "Aktuelle Bewerbungssituation" ...
..- attr(*, "names")=
2009 May 09
1
sqlSave()
Hi all: I have created a MS Access table named 'PredictedValues' through the statement below:
myDB <- odbcConnectAccess("C:/Documents and Settings/Owner/Desktop/Rpond Farming.mdb",uid="admin",pwd="")
sqlSave(myDB,PredictedValues,rownames=FALSE)
close(myDB)
But if I run the code again with new values I get the message below:
Error in sqlSave(myDB,
2003 Apr 02
1
RODBC sqlSave problem.
Dear list,
Being new to both the postgres database, ODBC and the RODBC interface, I
am somewhat confused by some of the problems I am experiencing trying to
connect R to the database.
Whai I am trying is basically the example part of the help file for the
sqlSave function:
> library(RODBC)
> odbcConnect("theodor") -> channel
> data(USArrests)
> sqlSave(channel,
2010 May 16
1
RODBC-Error-sqlSave
Dear R-community,
After repeating the sqlSave-command 3 times on a dataframe (of size 13149
rows * 5 columns) to my MS-Access database I get the following error:
*Error in sqlSave(channel, eksport_transp_acc_2, "transp_acc_scenarier", :
unable to append to table ‘transp_acc_scenarier’*
**
This means that the first 2 savings are completed, but the third-one
is somehow not. I have an
2005 Mar 15
0
Fwd: RODBC, sqlSave and sqlAppend
Début du message réexpédié :
> De: Depiereux Constant <constant.depiereux@aqte.be>
> Date: 16 mars 2005 00:11:11 GMT+01:00
> À: spjgmwn@iop.kcl.ac.uk
> Objet: Rép : [R] RODBC, sqlSave and sqlAppend
>
>
> Le 15-mars-05, à 16:19, Matthew W Nash a écrit :
>
>> Hi all,
>>
>> I am currently trying to read, write and append data between R and MS
2006 Feb 20
1
sqlSave
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
2007 Mar 07
0
sqlSave help!
Hi Everyone,
I'm so confused. I've been trying to save data to a table but I keep
getting an error that says the table
does not exist and at other times saying that it does. So here are some
statements:
> sqlQuery(channel, "select top 1 * from
> TestDB.[SILICON\\holouis1].clep_tier_shift")
State NB Change_Number
1 IL 2005-02-08 7
It exists and I
2018 Jan 24
1
Help with SQLsave
Hi all,
I'm using RODBC library to connect to a database.
I'm trying to read a table from a database and after manipulating it would like to write to the same database but with a different table
P<-data.frame(sqlQuery(myconn,'select? *? from Demographics'))
sqlSave(myconn,p,tablename="trial",rownames=FALSE)
I'm gettng this error
Version:1.0
2003 Apr 04
2
sqlSave() Question
All,
I am new in R. I found sqlSave() doesn't work for our Oracle9i. The
following was the message:
> sqlSave(channel, USArrests, rownames="state")
Error in sqlColumns(channel, tablename) : USArrests : table not found on
channel
Check case parameter in odbcConnect
>
sqlQuery() works OK.
Please help. Thanks.
-MY