On 10/31/2008 12:57 PM, Corrado wrote:
On Friday 31 October 2008 16:29:13 you wrote:
See Prof. Ripley's message. RODBC is passing a buffer and buffer size
to the ODBC driver, and that driver is overflowing the buffer. You
could probably hide this bug by making the buffer larger, but the real
fix is for the driver to take account of the buffer size it is being given.
1) How do you make the buffer bigger? Are we talking about increasing the
-- --param=ssp-buffer-size=4 at compilation time? would that solve the
problem, in your opinion?
I don't know. I wouldn't do that.
2) Why is this problem RODBC specific, if the problem is in the odbc driver?
Because the other packages pass bigger buffers, or generate different
messages?
I
do agree that RODBC passes buffer / buffer size, but why do other
applications work and RODBC does not? If the problem was with the driver,
then every other application linking to the same database through the same
driver would have the same problem, unless the other applications pass the
call (+ buffer / buffer size) in a different way.
Or if they ask the driver to do different things, or pass a different
size of buffer, etc. The fact that this only occurs for RODBC suggests
there's a problem there, but the fact that the driver is using sprintf
on a limited size of buffer is far stronger evidence that the problem is
in the driver.
Duncan Murdoch
Please, keep in mind I am just trying to solve a problem that other people may
have, because I am using standard installation.
Best,
--
Corrado Topi
Global Climate Change & Biodiversity Indicators
Area 18,Department of Biology
University of York, York, YO10 5YW, UK
Phone: + 44 (0) 1904 328645, E-mail: [EMAIL PROTECTED]
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
