Interesting. The basic SET TIMING ON / SET TIMING OFF commands work fine, using literal ON/OFF values, without substitution.
But even a trivial script using substitution, something like
ACCEPT VAL 'Enter ON or OFF'
SET TIMING &VAL.
suffers the same problem as your COL ... NEW_VALUE case. As for COL ... NEW_VALUE, it works fine from the worksheet in the following example I've borrowed...
create table new_value_test_from (
create table new_value_test_to (
insert into new_value_test_from values ('SQL Developer 4.0.1');
column some_field_name new_value some_var_name
select some_field_name from new_value_test_from;
insert into new_value_test_to values ('&some_var_name');
select * from new_value_test_to;
I'll log a bug -- thanks for taking the time to report this.
SQL Developer Team
Message was edited by: Gary Graham Bug 18309409 - FORUM: VARIABLE SUBSTITUTION NOT WORKING WITH SET TIMING SUBCOMMAND
Thanks for the response.
FYI, the issue is not limited to the TIMING subcommand. It is also present when using various other subcommands, e.g. ECHO, FEEDBACK, TERMOUT, VERIFY.
However, some subcommands do not have the issue, e.g. ESCAPE, HEADING.