For many databases, a LOAD is far faster than INSERT. For MySQL, for
instance, one can do a LOAD REMOTE where the file being loaded is remote
from the database even using JDBC. JDBC also allows for batching -- that
can help but the LOAD REMOTE approach is still better. (If you cannot
do the
Nice. We've been using dataport to slurp our database from oracle to
postgres with no trouble, but we have only a few blob columns and they
don't get that big.
I would've thought that the commit-based-on-number-of-bytes would've
been a sufficient fix. Was it necessary to use jdbc? Maybe that
On Jun 14, 2006, at 14:15, Bryan Lewis wrote:
I would've thought that the commit-based-on-number-of-bytes would've
been a sufficient fix. Was it necessary to use jdbc?
I will do some more testing with and without jdbc.
Maybe that was how you got the byte count.
Should be possible with
Joe,
Care to elaborate how this will work with a source database that is
not MySQL?
Andrus
On Jun 14, 2006, at 4:07 PM, McDaniel, Joe R. wrote:
For many databases, a LOAD is far faster than INSERT. For MySQL, for
instance, one can do a LOAD REMOTE where the file being loaded is
remote
Hi,
I'm not sure where to post it, but because I get this error by cayenne I try it
first here. A few days ago I reported a NPE within the class
apache.commons.map.LRUMap wich is used by the class DataRowStore. After
synchronizing all access to the corresponding field the NPE went away but now
While I don't have the answers, it would be helpful if you could
provide more details:
1. What version of commons-collections do you have (I checked 3.1 and
the line numbers do not match with the stack below)
2. Does it happen as a result of a certain sequence of events, or
does it happen
Hi Andrus,
I have not tried this except in MySQL. Basically, all one does is write
out a file and then call the LOAD for that file in JDBC exactly as if
one were working in a typical DB client tool. I ran across this in the
RDF database front-end to MySQL 3Store (also sometimes called
