Allright, this is driving me nuts. Going through a loop updating or inserting data into an Oracle table based on a flat file and I keep getting: Use of uninitialized value in numeric eq (==) at ParseFile.pl line 435, <INF> line ######. Simplified code:

my $lock = 0;
$GetDataFromTable->execute($indexnumber)
    || die "Can't execute GetDataFromTable ($DBI::errstr)";

unless (($lock,$updon) = $GetDataFromTable->fetchrow()) {
    $InsertData->execute($data1,$someotherdata,1,1,0)
        || die "Can't execute InsertData ($DBI::errstr)";
    goto DONE;
}
[download]

I evaluate some other unrelated data here, and here's the infamous line 435 that generates the warning.

if ($lock) {
     # Do some other stuffDon't mess with it, it's LOCKED!
}

elsif(...) {
    ...
}
else (...) {
    ...
}


DONE:
    #Do some stuff
[download]

It seems to me, the only way $lock could be uninitialized is for the fetchrow to have set it to undefined for not finding data in the table, in which case data is inserted and the line that generates the warning is skipped over. I've tried

if ($lock and 1) {
[download]

but it still generates the warning. The code works as I intend it to for all intents and purposes, but it spits out a lot of warnings, and I hate the idea of just shutting off the warning and ignoring it. Any ideas, and thanks. Blake Sorensen