[SOURCE] Issue #TRQS25 modified

[Martin Poeschl <mp...@marmot.at>]

Issue TRQS25 has just been modified by user mpoeschl

You can view the issue detail at the following URL:
     <http://scarab.werken.com/scarab/issues/id/TRQS25>

The following modifications were made to this issue:

Status changed from 'New' to 'Closed'

Comment:  the andDate method should be used
Resolution set to 'Invalid'

Comment:  the andDate method should be used

datadump and large databases

[Brian McCallister <mc...@forthillcompany.com>]

I posed this question on the users list, but it really belongs here.

Are there any significant differences between the datadump task in 3.0 
and 3.1? It presently fails with memory problems on large databases - 
while I realize it was never really meant for large database work, it 
sure as heck could be convenient tool for database migration if it did 
work nicely =)

The exact situation I am hitting is:

Using PostgreSQL 7.3.2, the org.postgresql.Driver current release 
version, about 600 megs of data on an uncompressed sql dump and 
allocating a 1.5 GB heap to ant I out of memory error part way through. 
This is on Torque 3.0 release

I haven't had a chance to look at the code, just wanted to ask if by 
chance 3.1 uses streamed data instead of apparently keeping a fairly 
large in-memory model of the whole thing =)

-Brian McCallister