Oracle suggests against using reserved words, but, in this case, it is TOAD's reaction to the word "TYPE"
which is causing the problem. Using straight SQL, the following works without problem:
create table test_table (type char(02));
insert into test_table values ('01');
commit;
select * from my_table;
update my_table
set type = '02'
where type = '01';
commit;
select * from my_table;
However, if you substitute the "update + commit" statement from above by performing the equivalent action
in the Schema Browser, TOAD rolls back the change. TOAD is the problem. It is not an option to change the field name.
WORKAROUND:
None.
STATUS:
Waiting for fix in a future release of Toad for Oracle.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center