Johannes,
On 1 March 2006 at 19:06, Steve Langasek wrote:
| On Wed, Mar 01, 2006 at 09:00:02PM -0600, Dirk Eddelbuettel wrote:
|
| > I just inherited this bug report. As I understand ODBC, the actual lifting
is
| > done by the ODBC driver of the RDBMS -- here MySQL. My casual look seems to
| > indicate that the segfault is there, so neither a r-cran-rodbc bug, nor (as
| > Steve determined) a odbcconfig bug.
|
| > But why r-cran-rodbc? That package has been very stable upstream, and
| > generally solid.
|
| Because the behavior when trying to issue a query using r-cran-rodbc is
| *not* a segfault, it's simply a failure to return the data, and this
| behavior was not reproducible with isql.
Did you try setting believeNRows=FALSE in odbcConnect() ? From
help(odbcConnect, package=RODBC):
odbcConnect(dsn, uid = "", pwd = "", case = "nochange",
believeNRows = TRUE)
[...]
believeNRows: logical. Is the number of rows returned by the ODBC
connection believable? Not true for Oracle and Sybase,
apparently.
This has been the fix on other systems, it could simply that RODBC gets
handed a bad value. Apparently common with some backends, as I recall I had
to use that too with some Sybase-on-Solaris versions a while back.
Dirk
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
