| Subject | Re: [firebird-support] Re: Inserting 100's of thousands from a SP |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-07-10T14:16:31Z |
At 01:04 PM 10/07/2005 +0000, you wrote:
procedures. CommitRetaining, with Snapshot isolation, might be useful if
you want all batches to operate on a consistent read-set.
The correct place to perform the batching for the stored procedure is at
the client. Define one or more input arguments for the start points for
your reads and return any "last values" you require as output arguments.
CommitRetaining, with Snapshot isolation, will be useful if you want all
batches to operate on a consistent view of the read-set.
You can keep your EXECUTE PROCEDURE call prepared for the whole duration of
the operation.
./hb
>Hi Bupp,It's not a valid suggestion. SUSPEND does not belong in executable
>Firebird has selectable procedures, unlike other systems.
>have you tried to do SUSPEND for every 10000 inserts and
>commitretaining them from client?
>only an idea, i am not sure if it is work.. i leaved the programming 6
>years ego.
procedures. CommitRetaining, with Snapshot isolation, might be useful if
you want all batches to operate on a consistent read-set.
The correct place to perform the batching for the stored procedure is at
the client. Define one or more input arguments for the start points for
your reads and return any "last values" you require as output arguments.
CommitRetaining, with Snapshot isolation, will be useful if you want all
batches to operate on a consistent view of the read-set.
You can keep your EXECUTE PROCEDURE call prepared for the whole duration of
the operation.
./hb