Stacy,
tom kyte's definitive oracle book references unwise
java programmers who adopt the max(id+1) plan.
it is not scalable, requires locking, forces full
scans of the entire id column (if it is indexed) or
full table scans if it is not. I am sure I am missing
many of the myriad reasons he dis
I've tried sequences, but if there is an error, the sequence
cannot be rolled back in any easy way and there are "gaps" in
the database :(
Stacy.
> not related to your problem, but
> use a sequence.
> the max(num+1) is a bad idea.
> --- Stacy Mader <[EMAIL PROTECTED]> wrote:
> >
> > Hi
not related to your problem, but
use a sequence.
the max(num+1) is a bad idea.
Job
--- Stacy Mader <[EMAIL PROTECTED]> wrote:
>
> Hi all.
>
> Using DBI 1.28 and DBD::Oracle 1.12 compiled against
> Oracle 8.1.7,
> I have the following:
>
> use strict;
> use DBI;
>
> $text = "This is a test.\n"
Hi all.
Using DBI 1.28 and DBD::Oracle 1.12 compiled against Oracle 8.1.7,
I have the following:
use strict;
use DBI;
$text = "This is a test.\n"x6000;
$sth = $dbh->prepare(qq{
DECLARE next NUMBER;
BEGIN
SELECT MAX(NUM+1) INTO next FROM REPORT;
INSERT INTO EXCESS
