Closed GoogleCodeExporter closed 9 years ago
It seems that we can't build up the batch too large. executeBatch() should be
called regularly. If we let the batch grow too large we get the following
strange error:
null: Ongeldige batchwaarde.
executeBatch() every 10,000 or every 1000? Test performance of 1000 or 10,000.
Original comment by rene.de....@gmail.com
on 16 Oct 2010 at 10:51
Streaming CSV implemented. An empty line signals the end. That might be a
problem when importing a single column where empty values are allowed. What's
the solution for that? Introduce a marker keyword?
IMPORT CSV INTO ATABLE UNTIL THEEND;
...CSV DATA...
THEEND
But that can be added later too.
Currently executeBatch() after 1000 records. Seems to have no negative impact
on performance. Needs to be tested with a database connected through the
network so that network latency will play its role.
Original comment by rene.de....@gmail.com
on 21 Oct 2010 at 8:59
[deleted comment]
Actually, importing a single column with empty values is already a problem for
the other form of import too, created issue #110 for that.
Original comment by rene.de....@gmail.com
on 21 Oct 2010 at 9:14
[deleted comment]
Also decided to go with RFC4180 and not strip whitespace from the values. Can
we make it optional?
IMPORT CSV IGNORE WHITESPACE
this will ignore whitespace except the whitespace between double quotes.
IMPORT CSV STRIP WHITESPACE
this will strip all whitespace even the whitespace between double quotes.
The IGNORE needs to be implemented first. Currently no need to implement STRIP.
Original comment by rene.de....@gmail.com
on 23 Oct 2010 at 11:27
This issue was closed by revision r534.
Original comment by rene.de....@gmail.com
on 23 Oct 2010 at 8:45
Original issue reported on code.google.com by
rene.de....@gmail.com
on 16 Oct 2010 at 9:42