Project

General

Profile

Bug #2223

ASSIGN schema triggers without reference to database fields

Added by Ovidiu Maxiniuc over 10 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version:

Related issues

Related to Database - Feature #2024: implement runtime support for database triggers Closed 06/19/2013 07/01/2013

History

#1 Updated by Ovidiu Maxiniuc over 10 years ago

  • Subject changed from Schema triggers without reference to database objects to ASSIGN schema triggers without reference to database fields
There are two kinds of ASSIGN schema triggers:
  • related to a well known database field (declared using TRIGGER PROCEDURE FOR ASSIGN OF <table>.<field> syntax). This is implemented and appears to work fine.
  • unrelated to any database field (declared using TRIGGER PROCEDURE FOR ASSIGN NEW [ VALUE ] <var_id> syntax).
The second syntax was not fully implemented and tested because of some issues:
  • inheritance from generified DatabaseTrigger. As there is no reference to database field, the class cannot declare/use its buffer type.
  • the conversion does the best effort to annotate it with correct values for SchemaTrigger annotation.
  • when trigger is fired, use the Undoable/BaseDataType signature method using the reference to the field from trigger's annotation or a copy of the actual value. The correct datatypes shoudl be checked and conversion should apply if possible or error must be raised.
  • the trigger is allowed to change the actual value, if the case, the updated value must be set back to respective property of affected buffer.

The issue was also documented in code.

At this moment the customer's server project does not use this form of the ASSIGN trigger so the implementation is delayed for a later moment.

#2 Updated by Greg Shah over 7 years ago

  • Target version deleted (24)

Also available in: Atom PDF