similar to: test version of RODBC

The first non-maintenance update of RODBC since January 2003 is now on CRAN and will soon propagate to mirrors. From the ChangeLog: * Select the decimal point from Sys.localeconv. * Add an external reference and finalizer so open channels get closed at the end of the session or when there is no R object referring to them. * There is no longer a

The first non-maintenance update of RODBC since January 2003 is now on CRAN and will soon propagate to mirrors. From the ChangeLog: * Select the decimal point from Sys.localeconv. * Add an external reference and finalizer so open channels get closed at the end of the session or when there is no R object referring to them. * There is no longer a

(1) I do read the posting guide (the fact that I missread o missunderstood something does not imply not reading) (2) I could change NAs to 0 (I know) but I have previously (older versions of R and SQL*Plus) used the same select with the "right" output (namely with 0s). (3) AFAIK "strange" is not a negative remark and does not seem to me at the very least but that is always a

One quirk to be watched is the use of connections to the DBMS via the Unix sockets vs ports. The PostgreSQL driver bundled with unixODBC will use Unix sockets to `localhost', but this driver seems unreliable (see the ChangeLog). The current driver will only use a TCP/IP port, and to use that needs postmaster started with the -i flag (which is not the default) and with tcp/ip

There is something strange in R behaviour (perhaps). I have run the same select in Oracle SQL*Plus (version 10.1.0.2.0) and the output comes out with NULLs (which is what it ougth to be). But in R I still get the same result with NAs (no matter I use na.strings or nullstring arguments) An output example follows below: Using na.string="0" and nullstring="0" (sorry by the

On behalf of Michael Lapsley, who is away. There is a new version of RODBC on CRAN, version 0.8-2. A version compiled for rw1011 will propagate to CRAN tonight. Main differences: - This will work with the up-coming R 1.2.0. - Nulls in databases are handled (more) correctly. The bug that has been reported with repeated entries was it transpires to do with null fields, not empty ones

Version 1.2.6 of RODBC is now on CRAN. This has a number of bug fixes and many workarounds for ODBC driver quirks--I've set up further testbeds for SQL Server 2008, Oracle and DB2. More visibly, the documentation has been expanded in several ways, in particular in collecting together advice on using 'schemas' and 'catalogs' in the ?RODBC overview. There is also a test

Version 1.2.6 of RODBC is now on CRAN. This has a number of bug fixes and many workarounds for ODBC driver quirks--I've set up further testbeds for SQL Server 2008, Oracle and DB2. More visibly, the documentation has been expanded in several ways, in particular in collecting together advice on using 'schemas' and 'catalogs' in the ?RODBC overview. There is also a test

Sorry, I was commenting on the previous windows version (version file says 0.5a) (the first one which ran under RW.1.0.0) I have Win NT 4.0 Service pack 5 and R is > version _ platform Windows arch x86 os Win32 system x86, Win32 status major 1 minor 0.0 year 2000 month February day 29 language R > -----Original Message----- > From: Prof Brian

Several of you have kindly sent me examples of bugs in RODBC, but none of them reproduce on my systems. I am fairly sure I know what is happening, and that it is client-specific. (Do empty strings get returned as "", NULL or skipped?) Also, empty character fields were getting mapped to NA. There's a comment in the code that fields need to set to a null string, and that was only

Under which version of R is it supposed to run ? With 1.1.0 under windows NT 4.0 against Access databases it doesn't work, I cannot get the name of the tables, every query I execute returns with "No Data". I'm surely doing something wrong ... Federico Spinazzi spinazzi@databankgroup.it Databank S.P.A Via Spartaco, 19, ITALY Tel. + 39 02 55002251 >Several of you have kindly

Your error message was >> d <- sqlFetch(channel, District) > Error in odbcTableExists(channel, sqtable) : > object "District" not found and as you had not defined an object 'District' in that session, it seems perfectly plain. If you want to refer to table "District" you have to give a character string (with quotes), not the name of an R

It seems to work smoothly now. Thank you very much. Federico Spinazzi spinazzi@databankgroup.it Databank S.P.A Via Spartaco, 19, ITALY Tel. + 39 02 55002251 -----Messaggio originale----- Da: Prof Brian Ripley <ripley@stats.ox.ac.uk> A: Federico Spinazzi <spinazzi@databankgroup.it> Cc: R-devel@r-project.org <R-devel@r-project.org> Data: lunedì 27 novembre 2000 11.03 Oggetto:

There is a new version of RODBC, 0.9-1, with a new maintainer (me) now on CRAN (Vienna) which works with R 1.6.x. The Windows binary will be there tomorrow, and both will then propagate around CRAN. This has been tested on Linux under unixODBC against MySQL and Postgresql (thanks to Dirk Edelbuettel), and on Windows against Access, MySQL and Excel. The CRAN compilation checks were against

There is a new version of RODBC, 0.9-1, with a new maintainer (me) now on CRAN (Vienna) which works with R 1.6.x. The Windows binary will be there tomorrow, and both will then propagate around CRAN. This has been tested on Linux under unixODBC against MySQL and Postgresql (thanks to Dirk Edelbuettel), and on Windows against Access, MySQL and Excel. The CRAN compilation checks were against

1. Can I avoid having RODBC use so much memory (35 times the data size or more) making a data.frame & then .rda file via. sqlQuery/save? 2. If not, is there some more appropriate way from w/in R to pull large data sets (2-5GB) into .rda files from sql? [R] reducing RODBC odbcQuery memory use? From: WILLIE, JILL <JILWIL_at_SAFECO.com> Date: Thu 25 Jan 2007 - 22:27:02 GMT

New to R, sorry if one or either of these is an inappropriate list for a question like this below; please let me know if this is a general help question. Jill Willie Open Seas Safeco Insurance jilwil at safeco.com -----Original Message----- From: WILLIE, JILL Sent: Thursday, January 25, 2007 2:27 PM To: r-help at stat.math.ethz.ch Subject: reducing RODBC odbcQuery memory use? Basic

Hi list members I have a vector of strings x=c("w","ex","ee") And I want to get a logical vector showing the positions where my search string "e" matches the elements partially, i.e. is at least the left-hand part of the target strings, i.e. I want to get a vector FALSE TRUE TRUE. Any ideas? Thanks Steve Powell proMENTE social research research |

One of R's goals has always been to run on minimal hardware, and we say for example (src/gnuwin32/CHANGES for rw1070) This version of R needs more memory and is slower to start up, because it loads more packages by default. This is only likely to be a concern on machines with 16Mb of memory or less than 300MHz processors. For such machines append R_DEFAULT_PACKAGES=ctest to the

essai <- odbcConnect("ORESTE_prod", uid="osis_r", pwd="12miss15" ,case="oracle") > sqlTables(essai)$ORESTE ... 1315 <NA> ORESTE S_PROFESSIONS_OLD TABLE <NA> 1316 <NA> ORESTE S_PROVENANCES TABLE <NA> 1317 <NA> ORESTE