Can't fix Error: PL/SQL Statement ignored

Question

I've just started working with Triggers. While trying to compile the next code fragment errors are listed in the log, like so: "Error(2,3): PL/SQL: SQL Statement ignored" and "Error(2,7): PL/SQL: ORA-00922: missing or invalid option". I don't understand the problem. Can anybody help?

CREATE OR REPLACE TRIGGER CONT_VIG
BEFORE INSERT ON CONTRACTS
FOR EACH ROW
WHEN (OLD.CLIENTID = NEW.CLIENTID AND OLD.ENDDATE > NEW.STARTDATE)

BEGIN
SET (OLD.enddate = :NEW.startdate-1);    
END;

`FOR EACH ROW` means for each row inserted - not for each row that exists in the table pre-insert. — MT0, Apr 19 '17 at 11:32
https://docs.oracle.com/database/121/LNPLS/create_trigger.htm lots of examples provided in the docs — kayakpim, Apr 19 '17 at 11:33
[Is this for the same assignment?](http://stackoverflow.com/q/43483253/266304) — Alex Poole, Apr 19 '17 at 11:42
First explain what are you trying to do - we cannot really comment on a code if we have no idea what are the requirements. — Goran Stefanović, Apr 19 '17 at 13:31
Where in the [PL/SQL manual](https://docs.oracle.com/database/121/LNPLS/fundamentals.htm#LNPLS00205) did you find the `SET` to assign values? — , Apr 19 '17 at 13:40

score 0 · Answer 1 · edited May 23 '17 at 12:32

0

look this this-oracle and this-stackoverflow

try this:

CREATE TRIGGER hr.salary_check
      BEFORE INSERT OR UPDATE OF salary, job_id ON hr.employees
      FOR EACH ROW
         WHEN (new.job_id <> 'AD_VP')
      pl/sql_block

edited May 23 '17 at 12:32

Community

1
1

answered Apr 19 '17 at 11:33

CompEng

7,161
16
68
122

score 0 · Answer 2 · answered Apr 19 '17 at 13:31

0

You can't change OLD value...

replace

SET (OLD.enddate = :NEW.startdate-1);

with for example :

:NEW.startdate := sysdate ;

(I removed SET because I don't see the usefulness)

answered Apr 19 '17 at 13:31

Jean-Christophe Blanchard

438
3
11

Removing SET has nothing to do with "usefulness" - it's plain wrong – Apr 19 '17 at 13:40
a_horse_with_no_name : yes – Jean-Christophe Blanchard Apr 19 '17 at 14:01

Can't fix Error: PL/SQL Statement ignored

2 Answers2

try this:

Linked