[Home] [Help]
4312: end if;
4313:
4314: SELECT hxc_approval_item_key_s.nextval
4315: INTO l_item_key
4316: FROM dual;
4317:
4318: update hxc_app_period_summary
4319: set notification_status = 'NOTIFIED',
4320: approval_item_type = itemtype,
4944: -- However, in 11g, with edition based redefinition available, even DBA_OBJECTS accesses a new table,
4945: -- SYS."_CURRENT_EDITION_OBJ".
4946: -- But we are going to the view instead of the SYS tables because of two reasons.
4947:
4948: -- 1. This is a dual maintained code, and we need the same code from 12.1 onwards. 12.1 is still allowed to
4949: -- to work in 10g, where this new SYS table is absent.
4950: -- 2. Even if we break dual checkin, the code wouldnt take the notation used. Even if it does, we are not
4951: -- sure if tomorrow we might need to change the whole query once again when the SYS table undergoes another feature change.
4952: --
4946: -- But we are going to the view instead of the SYS tables because of two reasons.
4947:
4948: -- 1. This is a dual maintained code, and we need the same code from 12.1 onwards. 12.1 is still allowed to
4949: -- to work in 10g, where this new SYS table is absent.
4950: -- 2. Even if we break dual checkin, the code wouldnt take the notation used. Even if it does, we are not
4951: -- sure if tomorrow we might need to change the whole query once again when the SYS table undergoes another feature change.
4952: --
4953: -- There sure is a perf trade off, but we chose the best view available. If there is a perf problem somehow in this
4954: -- functionality, we know where to look for and what to change.