Odtnhj

The conditions i create in case doesnt affect the apex calendar as they should this conditions are for workshifts that im creating in apex calendar.
Can someone help me it this conditions?

 create or replace PROCEDURE check_task_turnos AS
 BEGIN
 FOR i IN (SELECT ID, calendar_start, calendar_end, estado, TIPO,
 ,CASE
 when to_number(to_char(calendar_start,'DD')) = to_number(to_char(sysdate,'DD'))
 AND to_number(to_char(calendar_start,'HH24')) >= 7 AND to_number(to_char(calendar_end,'HH24')) < 15 
 AND to_number(to_char(sysdate,'HH24')) >= 7 AND to_number(to_char(sysdate,'HH24')) >= 15 
 then 'apex-cal-yellow'
 when to_number(to_char(calendar_start,'DD')) = to_number(to_char(sysdate,'DD'))
 AND to_number(to_char(calendar_start,'HH24')) >= 15 AND to_number(to_char(calendar_end,'HH24')) < 23 
 AND to_number(to_char(sysdate,'HH24')) >= 15 AND to_number(to_char(sysdate,'HH24')) >= 23 
 then 'apex-cal-yellow'
 when to_number(to_char(calendar_start,'DD')) = to_number(to_char(sysdate,'DD'))
 AND to_number(to_char(calendar_start,'HH24')) >= 23 AND to_number(to_char(calendar_end,'HH24')) < 7 
 AND to_number(to_char(sysdate,'HH24')) >= 23 AND to_number(to_char(sysdate,'HH24')) >= 7 
 then 'apex-cal-yellow'
 else null end
 FROM PASSAGEM
 where estado='Aceite'
 and TIPO='To Do'
 )

 LOOP
 -- registo no LOG , aqui nao registas na PASSAGEM, registas numa tabela ao lado de LOG para teres referencia de quando foi alterada a data da tarefa
 INSERT INTO PASSAGEM_LOG(passagem_id,
 start_date,
 end_date 
 )
 VALUES(i.id , 
 i.calendar_start+( 8/24) ,
 i.calendar_end +(8/24));
 -- update das horas de inico e fim para posicionamento no calendario
 UPDATE PASSAGEM
 SET calendar_start = i.calendar_start+(8/24) --incrementamos 8horas (periodod e um turno
 ,calendar_end = i.calendar_end+(8/24) --incrementamos 8horas (periodod e um turno
 WHERE ID = i.ID;
 END LOOP;
 COMMIT;
 END;

You should really learn how to properly format code; the one you posted is difficult to read and understand.

As of your question: this procedure uses a cursor FOR loop. That long, ugly CASE

• doesn't have an alias


• is never used later in procedure code
  
  
  • if you plan to use it, set its alias (e.g. my_case) so that you could reference it as i.my_case
    
  
  

So, why do you expect it to do anything, anywhere? The way it is now, as if CASE was never written.