search for: dbexec

...l_sendevent) exten => _911X.,n(lbl_setcall),Set(IDGCALL=0) exten => _911X.,n(lbl_sendevent),Gotoif($["${DBTYPE}"="SQL"]?lbl_sql:) exten => _911X.,n,Gotoif($["${DBTYPE}"="MYSQL"]?lbl_mysql:lbl_record) exten => _911X.,n(lbl_sql),UserEvent(${CHANNEL}$DBEXEC$EXEC udsp_vlog_start_record '${CHANNEL}'#'${IDGTERMINAL}'#'${EXTEN:1}'#'${FILENAME}'#'${UNIQUEID}'#'${CALLERID(num)}'#'O'#${VLOGSERVER}#'${HTTPPATH}${RECORDFILENAME}'#${IDGCALL}$) exten => _911X.,n,Goto(lbl_record) exten => _911X...

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

Hi all, This is a potentially very stupid question about MySQL <-> R interaction, but I have not been able to solve it. I'm just trying to connect R to my MySQL databse, and gets this: > library(RMySQL) Loading required package: methods > m <- dbDriver("MySQL") > con <- dbConnect(m,group="testdb") Process R segmentation fault at Wed Oct 16 07:04:30

I've been putting together a package that defined generic methods for database access. The packages is called "Rdbi." It borrows as much as possible from existing database packages / proposals. I'd like to start a discussion about the proposed interface. Here's what I've come up with so far: # # Rdbi: connectionMethods.R # dbConnect <- function(dbObj, ...)