Set Record-Status to Query after a POST-QUERY

In a block with a POST-QUERY-trigger you often have the problem, that the Record-Status changes to CHANGED, if non-basetable-items were changed through the POST-QUERY.

Setting the recordstatus back to QUERY is a good method to solve this problem. First create a procedure for setting the record-status to QUERY:

PROCEDURE Set_Record_Query_Status IS 
BEGIN
  Set_Record_Property (NAME_IN ('SYSTEM.TRIGGER_RECORD'), 
                       NAME_IN ('SYSTEM.TRIGGER_BLOCK'), 
                       STATUS, 
                       QUERY_STATUS);
END; 

then use it in your POST-QUERY-triggers:

BEGIN
  SELECT someColumns
    INTO :myBlock.nonBasetable_Item
    FROM myTable
   WHERE someFilter;

  Set_Record_Query_Status;
END;

After resetting each record to QUERY-Status you don't have problems with the fetched data in this block.

Important: If the POST-QUERY changes Basetable-Items in the record you create record-locks, if the block-locking is Immediate. This problem can be solved:

BEGIN
  Set_Block_Property ('myBlock', LOCKING_MODE, Delayed);

  SELECT someColumns
    INTO :myBlock.nonBasetable_Item
    FROM myTable
   WHERE someFilter;

  Set_Block_Property ('myBlock', LOCKING_MODE, Immediate);

  Set_Record_Query_Status;
END;

try it
Gerd