similar to: How to call stored procedure on iodbc

Hello, We are having some strange issues with RODBC related to integer columns. Whenever we do a sql query the data in a integer column is 150 actual data points then 150 0's then 150 actual data points then 150 0's. However, our database actually has numbers where the 0's are filled in. Furthermore, other datatypes do not have this problem: double and varchar are correct and do not

How does one get asterisk to timeout realtime request via res_odbc to unixODBC? I've set timeouts as appropriate for freetds (which unixODBC is using.) However, it doesn't seem to work. It takes over 3 minutes to timeout a connection and queries never seem to timeout, so a channel waiting on a query never terminates. I did notice that res_odbc.c never sets a timeout on the query

maybe someone here can help me understand why I am getting this strange behaivor. I am connecting to a MS SQL server from PHP by the ODBC module, I use unixODBC-2.2.9-1, freetds-0.63-1.2.el4.rf and php-4.3.9-3.9 all but the freetds package came with CentOS-4.2 + updates the problem is that I am getting -1 from the odbc_num_rows(); function, I search the net and it looks that this is a very

Hello, I've got a problem in a sql query! for(j in 1:length(criteria$Title)) { graphe_par<-sqlQuery(channel,"select q.type,crit.Title, r.Value from criteria crit, reply r,question_reply qr, question q, question_criteria qc, form_question fq where qr.reply=r.ID and qr.question=q.ID and qc.question=q.ID and crit.ID=qc.criteria and fq.question=q.ID and fq.form=4 and

For those R user's who don't subscribe to R-sig-db and are having troubles with the latest RMySQL binary on CRAN, please read the email thread at the end of this message. RMySQL 0.7-2 does work with MySQL 5.1, however the CRAN binary is linked against the 5.0 version. Best, Jeff -------- Original Message -------- Subject: Re: [R-sig-DB] Problems with RMySQL and MySQL server version

Both of our production asterisk servers are dumping core when making writes to our cdr tables. Here is a backtrace of the problems we are having: #0 0x00447b1f in tdserror (tds_ctx=0x1, tds=0xb7938c90, msgno=20004, errnum=9) at util.c:347 347 if (tds_ctx && tds_ctx->err_handler) { (gdb) bt #0 0x00447b1f in tdserror (tds_ctx=0x1, tds=0xb7938c90, msgno=20004, errnum=9) at

Dear List, Would anyone know how to perform prepared queries with ROBC ? I had a shot with some of the internal (non-exported) functions of the package but ended up with a segfault, so I prefer asking around before experimenting further... Thanks, Laurent