Issue 38 in rpostgresql: Incorrect Error Message

4 views
Skip to first unread message

rpost...@googlecode.com

unread,
Jan 13, 2012, 9:56:22 PM1/13/12
to rpostgr...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 38 by ashwin.k...@gmail.com: Incorrect Error Message
http://code.google.com/p/rpostgresql/issues/detail?id=38

What steps will reproduce the problem?

1. Run Postgres with some data in a table

2. Do dbGetQuery("query"). The query should return some rows from a table.

3. Get a bad error message once for each select "unrecognized PostgreSQL
field type void (id: 2278) in column 0.

What is the expected output? What do you see instead?
The error message should not be there.

What version of the product are you using? On what operating system?
Postgres 9.1. Running Mac OSX Lion R 2.14.1

Please provide any additional information below.
Simple fix. Add the lines

case VOIDOID:
break;

after line 546 in RS-PostgreSQL.c.

Basically column 0 on every select is of type void.

rpost...@googlecode.com

unread,
Jan 21, 2012, 4:29:51 AM1/21/12
to rpostgr...@googlegroups.com

Comment #1 on issue 38 by tomoa...@kenroku.kanazawa-u.ac.jp: Incorrect
Error Message
http://code.google.com/p/rpostgresql/issues/detail?id=38

Thanks for the report.

However, this report was not reproducible, as the detail on the "some data"
and "query" is not provided. So far as tested, the iris dataset stored
with dbWriteTable(), and "select * from iris" does not produce the above
error on OS X 10.6.8 (R 2.14.0, RPostgreSQL installed from binary package)
connected with 9.1.2 server running on another machine.

The error message can be produced with
dbGetQuery(con,"select NULL::void")
However, in this case, the warning is reasonable as it is unclear how to
handle
the void type.

So, I suspect that "query" is in fact a function that really returns a void
type, for which we do not have determined what is the right way to handle.

rpost...@googlecode.com

unread,
Oct 9, 2012, 5:27:47 AM10/9/12
to rpostgr...@googlegroups.com
Updates:
Status: Invalid

Comment #2 on issue 38 by tomoa...@kenroku.kanazawa-u.ac.jp: Incorrect
Error Message
http://code.google.com/p/rpostgresql/issues/detail?id=38

This is closed because no concrete way to reproduce the problem is provided.

Reply all
Reply to author
Forward
0 new messages