>>For example in Java the default result set is forward only. If it doesn't
>>have rows, it will fetch a number (default is 400 in Jaybird), this is done
>>through a fetch. It will then serve requests for rows from the application
>>from this retrieved set of rows. When it needs more, it discards t
On Fri, 19 Jun 2015 14:48:44 +, "'Leyne, Sean'
s...@broadviewsoftware.com [firebird-support]"
wrote:
>> what is the proper way for copy data from big table to another database
>> if table is bigger then avaiable RAM and we need to do this in one
>> transaction?
>> You know if we do
>> SELECT *
On Fri, 19 Jun 2015 16:43:37 +0200, "Mark Rotteveel m...@lawinegevaar.nl
[firebird-support]" wrote:
> The proper way to do this is to execute a single query, and interleave
> fetching of rows from the source with inserting rows into the target.
That
> should work without consuming all memory as lo
> what is the proper way for copy data from big table to another database
> if table is bigger then avaiable RAM and we need to do this in one
> transaction?
> You know if we do
> SELECT * FROM SOURCE_TABLE - and table have e.g. 400 000 000 records
> then retrive it is impossible because of RAM
On Fri, 19 Jun 2015 15:20:39 +0200, "liviuslivius
liviusliv...@poczta.onet.pl [firebird-support]"
wrote:
> what is the proper way for copy data from big table to another database
> if table is bigger then avaiable RAM and we need to do this in one
> transaction?
> You know if we do
> SELECT * FROM
en this is not simple. And also if table
have no key at all.
Regards,
Karol Bieniaszewski
- Reply message -
Od: "Lester Caine les...@lsces.co.uk [firebird-support]"
Do:
Temat: [firebird-support] Proper way for copy data from big table
Data: pt., cze 19, 2015 15:58
On 19/06/15
On 19/06/15 14:20, liviuslivius liviusliv...@poczta.onet.pl
[firebird-support] wrote:
> SELECT FIRST 100 SKIP 0 * FROM SOURCE_TABLE <-we got 100 reads -> ok
> SELECT FIRST 100 SKIP 100 * FROM SOURCE_TABLE <-we got 200
> reads -> not ok
> SELECT FIRST 100 SKIP 200 * FRO
Hi,
what is the proper way for copy data from big table to another database
if table is bigger then avaiable RAM and we need to do this in one transaction?
You know if we do
SELECT * FROM SOURCE_TABLE - and table have e.g. 400 000 000 records
then retrive it is impossible because of RAM
but if
