similar to: RODBC tables

Hi all, Have a problem. Trying to read in a data set that has about 112,000,000 rows and 8 columns and obviously enough it was too big for R to handle. The columns are mode up of 2 integer columns and 6 logical columns. The text file is about 4.2 Gb in size. Also I have 4 Gb of RAM and 218 Gb of available space on the hard drive. I tried the dumpDF function but it was too big. Also tried bring in

Hello, I am not able to query Sybase IQ database from R using RODBC package. Check the below code R> sybaseiq.query <- function (sql, ..., as.is = FALSE) { connstr <- "Driver={Sybase IQ};UID=ajadhav2;PWD=*****;ServerName=PSGSESHR01A_IQ;CommLinks=SharedMemory,TCPIP{host=psgseshr01_iq.sg.csfb.com;port=3051}" chan <- odbcDriverConnect(connstr)

I have compiled and linked a 64 bit version of R (R 2.9.2) and the corresponding unix ODBC 64 bit package The red highlighted text below is the error I'm getting trying to when invoking a sqlQuery > library(RODBC) > channel <- odbcConnect("OraLSH", <user>, <password>) > sqlQuery(channel,"select sysdate from dual") Error in .Call(C_RODBCFetchRows,

I have compiled and linked a 64 bit version of R (R 2.9.2) and the corresponding unix ODBC 64 bit package When issuing a SqlQuery, I get the following error > library(RODBC) > channel <- odbcConnect("OraLSH", <user>, <password>) > sqlQuery(channel,"select sysdate from dual") Error in .Call(C_RODBCFetchRows, attr(channel, "handle_ptr"), max,

I have compiled and linked a 64 bit version of R (R 2.9.2) and the corresponding unix ODBC 64 bit package When issuing a SqlQuery, I get the following error > library(RODBC) > channel <- odbcConnect("OraLSH", <user>, <password>) > sqlQuery(channel,"select sysdate from dual") Error in .Call(C_RODBCFetchRows, attr(channel, "handle_ptr"), max,

What is this error message about and how do I troubleshoot it? > sqlTables(channel) Error in .Call("RODBCFetchRows", attr(channel, "handle_ptr"), max, buffsize, : negative length vectors are not allowed The channel was created as such channel <- odbcConnect("Labdata") I think this is telling me that my odbcConnect command worked >

Dear R Gurus, I would very much appreciate some help with this code snippit from my RODBC package. R crashes or exhibits bizarre behaviour when repeatedly fetching large numbers of rows. Examples: > odbcFetchRows(0,max=50000)->xx > odbcFetchRows(0,max=50000)->xx > odbcFetchRows(0,max=50000)->xx > odbcFetchRows(0,max=50000)->xx > odbcFetchRows(0,max=50000)->xx 3rd

Hello... After installing the precompiled version of R 2.1.0 (congratulations to the R Development Core Team) for Windows XP (Service Pack 2), I'm having problems with the "odbcCloseAll" and "odbcClose" functions within the "RODBC" package. I get pretty much the same error message for both functions: odbcCloseAll() produces: Error in

On Friday 18 December 2009 17:27, David Greene wrote: > > Here's the updated patch. > > Well, that didn't go through right. Here it is again. Argh! Stupid bug fixed. :) Index: include/llvm/Support/circular_raw_ostream.h =================================================================== --- include/llvm/Support/circular_raw_ostream.h (revision 0) +++

On Friday 18 December 2009 13:56, David Greene wrote: > On Friday 18 December 2009 13:53, David Greene wrote: > > > > + void releaseStream() { > > > > + // Delete the stream if needed. Otherwise, transfer the buffer > > > > + // settings from this raw_ostream back to the underlying > > > > stream. + if (!TheStream) > > >

On Dec 18, 2009, at 3:46 PM, David Greene wrote: > > + /// circular_raw_ostream - A raw_ostream that saves its output in a > + /// circular buffer. A better description would be "which *can* save its data to a circular buffer, or can pass it through directly to an underlying stream if specified with a buffer of zero." When it is buffering, what causes it to flush? Your

Hi, I'm trying to connect to a Teradata database via RODBC on a Linux 64 machine (Red Hat Enterprise Linux 5). The ODBC driver is properly configured and queries sent via unixODBC's isql tool work properly. However, this is what happens when I try to connect via RODBC: > library(RODBC) > conn = odbcConnect("thedsn", uid="theuid", pwd="thepass") ***

On Friday 18 December 2009 17:22, David Greene wrote: > On Friday 18 December 2009 13:56, David Greene wrote: > > On Friday 18 December 2009 13:53, David Greene wrote: > > > > > + void releaseStream() { > > > > > + // Delete the stream if needed. Otherwise, transfer the > > > > > buffer + // settings from this raw_ostream back to

On Wednesday 16 December 2009 13:35, David Greene wrote: > > Please make BufferSize an 'unsigned' and default it to 8192. Please use > > PRESERVE_STREAM instead of 'false'. Here's an updated version of the circular buffer. Ok to check in? -Dave Index: include/llvm/Support/circular_raw_ostream.h

On Friday 18 December 2009 19:47, Chris Lattner wrote: > On Dec 18, 2009, at 3:46 PM, David Greene wrote: > > + /// circular_raw_ostream - A raw_ostream that saves its output in a > > + /// circular buffer. > > A better description would be "which *can* save its data to a circular > buffer, or can pass it through directly to an underlying stream if > specified

On Dec 17, 2009, at 3:41 PM, David Greene wrote: > On Wednesday 16 December 2009 13:35, David Greene wrote: > >>> Please make BufferSize an 'unsigned' and default it to 8192. Please use >>> PRESERVE_STREAM instead of 'false'. > > Here's an updated version of the circular buffer. Ok to check in? This is looking a lot better, here are some more

Dear R-SIG-Debian, while trying to query data from an SQLite database through RODBC on Debian testing, R crashes with the following message: library(RODBC) con3 <- odbcConnect("test3") # 'test3' being an ODBC datasource configured with SQLite3 driver, # but the same happens with SQLite driver sqlQuery(con3, "select * from test") # 'test' being any table

On Friday 18 December 2009 12:28, Chris Lattner wrote: > This is looking a lot better, here are some more comments: > > + /// current_pos - Return the current position within the stream, > > + /// not counting the bytes currently in the buffer. > > + virtual uint64_t current_pos() { > > I didn't notice this earlier, but is there any reason for current_pos

On Friday 18 December 2009 13:53, David Greene wrote: > > > + void releaseStream() { > > > + // Delete the stream if needed. Otherwise, transfer the buffer > > > + // settings from this raw_ostream back to the underlying stream. > > > + if (!TheStream) > > > + return; > > > + if (DeleteStream) > > > +

On Friday 18 December 2009 20:20, David Greene wrote: > I wanted something to signify in the output where the debug dump starts. > That's for that case where some stuff might still get output through > errs(). I anticipate that while I'll change most uses of errs() to dbgs(), > we probably don't want to change all of them. > > I agree the naming here is poor.