Rob,
There have been a few reports of issues with the default value of 100 for
rows_at_time and I have had issues on OSX connecting to an Oracle server. I
have set the value to 1 in the wrapper functions that I have written to obtain
data from our server where I call odbcConnect() and
Hello,
We are having some strange issues with RODBC related to integer columns.
Whenever we do a sql query the data in a integer column is 150 actual data
points then 150 0's then 150 actual data points then 150 0's. However, our
database actually has numbers where the 0's are filled in.
some more info
t(t(odbcGetInfo(connection)))
[,1]
DBMS_NameAdaptive Server Anywhere
DBMS_Ver 12.70.
Driver_ODBC_Ver 03.51
Data_Source_Name dbname
Driver_Name Adaptive Server Anywhere
Driver_Ver 09.00.0001
ODBC_Ver 03.52.
Server_Name
It turns out that in the sqlQuery I must set rows_at_time =0 to get rid of
this problem.
Does anyone have any idea why this might be?
On Tue, Feb 16, 2010 at 12:52 PM, Rob Forler rfor...@uchicago.edu wrote:
some more info
t(t(odbcGetInfo(connection)))
[,1]
DBMS_Name
4 matches
Mail list logo