R help - Mar 2010 - MySQL and RODBC - limitations

Hello,

By accident I fell over a problem, which just did not expected...

Via Windows ODBC (package RODBC) I download data from a MySQL 5.1 database.
The amount is so large that the working set memory is going up to around
400MB. Not too large, I think.

Anyhow, one column includes ten digit numbers. Somehow, not all of these
numbers are displayed correctly. At some point all numbers turn to
"2147483647". I am aware of the meaning of the number (2GB). However,
where
is the problem? Is it the connector or R?

I set the flag in the ODBC Connector "Allow big results flag", but I
see no
difference. Any ideas what I can do?

Thank you!
 jorgusch
-- 
View this message in context:
http://n4.nabble.com/MySQL-and-RODBC-limitations-tp1692743p1692743.html
Sent from the R help mailing list archive at Nabble.com.

I found the solution.
The problem was indeed R. 

Their is a simple way to solve the problem, but it just needs a bit more
time. 
If you download large integers from a database, convert it "on the
fly" with

SELECT CONVERT(yourcolumn,char)

That is it. This is nor problem, as long you do NO comparisons within this
columns. If you want to find something like entry10>entry11
('13'>'2') than
the result will be wrong, if both values do not have the same number of
characters. Hence, if you have numbers, you must fill up the empty slotes
with zeros. So it would look like:  '13'>'02'.
-- 
View this message in context:
http://n4.nabble.com/MySQL-and-RODBC-limitations-tp1692743p1745570.html
Sent from the R help mailing list archive at Nabble.com.