Displaying 3 results from an estimated 3 matches for "mysqlresultset".
2002 May 17
1
RMySQL/methods problem
...L);
m<-dbManager('MySQL')
con<-dbConnect(m);
quickSQL(con, ' select blah blah..');
This works fine . However when I then do:
library(methods);
and then repeat my sql :
quickSQL(con, ' select blah blah..');
I get the following error:
Error in getClass(Class) : "MySQLResultSet" is not a defined class.
Is this a bug or am I doing something wrong.
Many thanks
Rob.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or &quo...
2001 Aug 17
0
making a neat timetable
On Fri, 17 Aug 2001, Patrick Connolly wrote:
> |> The data are stored in a MySQL table, and I can read them
> |> into R with RMySQL obtaining a MySQLResultSet object (which I
> |> suppose is a data frame ?) which looks like this:
>
> No, it doesn't have any column names. It would be a good idea to get
> it into one since dataframes are very good ways of manipulating this
> kind of data.
I've found out it does actually:
> s...
2002 Aug 09
2
RMySQL fetch defaults to N=500?
It appears that fetch() gets only the first 500 rows by default. I
don't see this in the documentation, but
timeinfo <- fetch(rs)
gets only 500 rows where
timeinfo <- fetch(rs,n=-1)
gets (correctly) 736 for the same query. Is this an undocumented
feature? I played with this data for an alarming amount of time
before I realized that I was missing a third of the data. I