Hello, For me, using RdbiPgSQL, logical columns in the result of a dbGetQuery contain only false values, even if the database rows contain true values (statgen is an open connection to a PostgreSQL database): > dbGetQuery(statgen, "SELECT true;") bool 1 FALSE RdbiPgSQL versions: 1.0.2, 1.0.5 Postgres client lib versions: postgresql-libs-7.4.1-1PGDG, postgresql-libs-7.3.4-11 Postgres server version: postgresql-7.4.1-1PGDG The attached patch appears to solve the problem for me. With the patch applied: > dbGetQuery(statgen, "SELECT true;") bool 1 TRUE I'm assuming that the BioConductor list is the place to send this, since I got RdbiPgSQL from BioConductor in the first place. If not, please point me in the right direction. Regards, Mitch -------------- next part -------------- A non-text attachment was scrubbed... Name: RdbiPgSQL.diff Type: text/x-patch Size: 348 bytes Desc: not available Url : https://www.stat.math.ethz.ch/pipermail/bioconductor/attachments /20040412/b8edc94b/RdbiPgSQL.bin

>The attached patch appears to solve the problem for me. >With the patch applied: Yes, a string comparison should be used. The bug has been fixed and will be removed from tomorrow's build of RdbiPgSQL. Thank you very much. > >> dbGetQuery(statgen, "SELECT true;") > bool >1 TRUE > >I'm assuming that the BioConductor list is the place to send this, since >I got RdbiPgSQL from BioConductor in the first place. If not, please >point me in the right direction. > >Regards, >Mitch Jianhua Zhang Department of Biostatistics Dana-Farber Cancer Institute 44 Binney Street Boston, MA 02115-6084