You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitted by Patrick Jolliffe: http://www.talkapex.com/2013/06/logger-200-released.html - it does not currently compile on 10g database (cannot use SEQUENCE.NEXTVAL directly in trigger, have to insert into a local variable).
Add a new variable l_lt_11_2 varchar2(50) := 'FALSE';
Modify it
if l_version <11 then
l_lt_11_2 :='TRUE';
else
l_lt_11_2 :='FALSE';
end if;
...
l_variables := l_variables||'LT_11_2:'||l_lt_11_2||',';
M bi_logger_logs (in logger_logs)
-- Oracle 10 and below require a SELECT INTO for nextval;
$IF $$LT_11_2 $THEN
selectlogger_logs_seq.nextval into :new.idfrom dual;
$ELSE
:new.id :=logger_logs_seq.nextval;
$END
Due to conditional compilation this will raise an error during initial compiling on 10g databases. The installer will running logger_configure at the end which will resolve the trigger error and it then works fine in 10g (i.e. ignore the initial error).
Submitted by Patrick Jolliffe: http://www.talkapex.com/2013/06/logger-200-released.html - it does not currently compile on 10g database (cannot use SEQUENCE.NEXTVAL directly in trigger, have to insert into a local variable).
Update: .nextval is only available in PL/SQL starting with 11gR2 onwards: http://docs.oracle.com/cd/B28359_01/server.111/b28279/chapter1.htm#FEATURENO07450
The text was updated successfully, but these errors were encountered: