I have a table in mysql that has 44,383,225 records, but when I do a pull, the postgres table ends up with significantly fewer records. I have run the process twice, getting 40,150,338 on the first attempt, and 40,033,964 on the second (even tho nothing was done to the mysql table).
No errors are generated on either the client or the server (as far as I can tell: the server has screens full of lines like "127.0.0.1 - tmpuser [17/May/2013 10:00:55] "POST /sessions/1106191956/pull/table HTTP/1.1" 200 - 1.1605", but the screen buffer only goes back about 10 screens worth).
I am running both the client and the server on the same machine, in 2 different terminal windows on Ubuntu 10.04 LTS.
PS: I got the postgres record count by doing "select count(*) from pricedata" (same with mysql). And, fwiw, that gave me the same number as when I ran "Count" from the context menu of that table n pgAdmin III v1.16.1.
I have a table in mysql that has 44,383,225 records, but when I do a pull, the postgres table ends up with significantly fewer records. I have run the process twice, getting 40,150,338 on the first attempt, and 40,033,964 on the second (even tho nothing was done to the mysql table).
Here's the syntax I'm using:
server: taps server mysql://root:mypassword@localhost/QE2Database tmpuser tmppass client: taps pull postgres://postgres:mypassword@localhost/QE2Database http://tmpuser:tmppass@localhost:5000
No errors are generated on either the client or the server (as far as I can tell: the server has screens full of lines like "127.0.0.1 - tmpuser [17/May/2013 10:00:55] "POST /sessions/1106191956/pull/table HTTP/1.1" 200 - 1.1605", but the screen buffer only goes back about 10 screens worth).
I am running both the client and the server on the same machine, in 2 different terminal windows on Ubuntu 10.04 LTS.
PS: I got the postgres record count by doing "select count(*) from pricedata" (same with mysql). And, fwiw, that gave me the same number as when I ran "Count" from the context menu of that table n pgAdmin III v1.16.1.