On Tue, Feb 28, 2006 at 02:59:36PM +0100, Johannes Ranke wrote:
> Package: unixodbc
> Version: 2.2.11-9
> Severity: important

> The combination of unixodbc, libmyodbc and r-cran-rodbc works nicely on 
> a couple of i386 (debian unstable) and one amd64 (debian stable) boxes.

> On this machine, I am running pure amd64 unstable, and I get a very
> strange behavior with ODBC connections to my local mysql database:

> A php test script

>       <?php
>       $dbh = odbc_connect('cytotox', 'cytotox', 'cytotox') or 
> die(odbc_errormsg() );
>       ?>

> just segfaults. strace ends with

strace is useless for debugging a segfault.  Please run your test script
under gdb and forward the backtrace. 

http://wiki.debian.org/HowToGetABacktrace

>       > tables <- sqlQuery(channel,query,errors=TRUE)
>       > tables
>       [1] "[RODBC] ERROR: Could not SQLExecDirect"                            
>                                                
>       [2] "S0022 1054 [unixODBC][MySQL][ODBC 3.51
>       Driver][mysqld-5.0.18-Debian_8-log]Unknown column 'plates' in 'field
>       list'"

> but if I use the correct column name, it returns an empty set 

>       > query <- "select plate from plates"
>       >  tables <- sqlQuery(channel,query,errors=TRUE)
>       >  tables
>       character(0)
>       > odbcGetErrMsg(channel)
>       character(0)

> although the same query issued with the mysql command line client (and
> same username and password) gives 1202 rows.

And what happens if you issue the query using the isql commandline tool?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to