Functionality og the code

Question

Hi ,
We have the following code. I am not getting the functionality of the code. Please have a look into the code and let me know the functionality.
BEGIN
                INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
                VALUES  ('Y',SYSDATE,'SUCCESSFUL');
                        --COMMIT;
           EXCEPTION
           WHEN OTHERS THEN
               NULL;
    END;
   --COMMIT;
  ELSE
   BEGIN
       INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
                VALUES  ('N',SYSDATE,'COUNT 0');
       EXCEPTION
              WHEN OTHERS THEN
                    NULL;
        END;
        --COMMIT;
   END IF;
  END IF;
    IF  var1 >0 THEN
             COMMIT;
   ELSE
        ROLLBACK;
                INSERT INTO tab1(sucess_flag ,run_DATE,comments)
                VALUES  ('N',SYSDATE,'UNSUCCESSFUL-0 Rec.');
                        COMMIT;
        END IF;
    EXCEPTION
        WHEN OTHERS THEN
                INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
                VALUES  ('N',SYSDATE,'UNSUCCESSFUL');
                        COMMIT;
END; Thanks,
Ora.

Answer 1

Hi,
Can you be more specific about what you don't understand? For example:
966949 wrote:
Hi ,
We have the following code. I am not getting the functionality of the code. Please have a look into the code and let me know the functionality.
BEGIN
INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
VALUES  ('Y',SYSDATE,'SUCCESSFUL');
--COMMIT;
do you understand that the part above attempts to add a row to the tab1 table? Do you need to have someone explain what tab1 is, or what 'Y' means?
EXCEPTION
WHEN OTHERS THEN
NULL;
END;The EXCEPTION section above ignores any error that may occur in the corresponding BEGIN section (the INSERT statement, in this case).
By the way, "EXCEPTION WHEN OTHERS NULL;" is almost always a terrible programming practice. You should only use use "WHEN OTHERS" if you want to do something special before raising the error; that is, 'WHEN OTHERS" should always be followed, sooner or later, by "RAISE;".
{code}
--COMMIT;
ELSE
BEGIN
INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
VALUES ('N',SYSDATE,'COUNT 0');
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
--COMMIT;
{code}Like the preceding code, this is attempting to add a row to a table, and ignoring any errors that may cause.
{code}
END IF;
END IF;
{code}Apparantly, what you posted is taken out of context. These two END IF statements should have corresponding IF statements.
{code}
IF var1 >0 THEN
COMMIT;
ELSE
ROLLBACK;
INSERT INTO tab1(sucess_flag ,run_DATE,comments)
VALUES ('N',SYSDATE,'UNSUCCESSFUL-0 Rec.');
COMMIT;
END IF;
EXCEPTION
WHEN OTHERS THEN
INSERT INTO tab1 (sucess_flag ,run_DATE,comments)
VALUES ('N',SYSDATE,'UNSUCCESSFUL');
COMMIT;
END;
{code}It's very hard to make sensible comments on the code without seeing all the code. Also, it helps to have test versions of any tables referenced (CREATE TABLE and INSERT statements).
My best guess, based on the fragment you posted, is that tab1 is a log table. The code you posted adds messages to that log table, based on whether some other statements (which you didn't show, but apparantly occur earlier in the code) worked or not.