Oracle Idiosyncrasies

Again stumbling upon  internet, I found interesting staff about Oracle by Yong Huang who claims we can’t find anywhere else about what he wrote. Before checking out his web page lets prove one bug like thing he wrote about comments in Oracle.

hr@XE> drop table t PURGE; Table dropped. sys@XE> drop table t purge; Table dropped. sys@XE> create table t (a number); Table created. sys@XE> insert into t values (123); 1 row created. sys@XE> /*update T set a=321 where a=123;*/ 1 row created. sys@XE> /*insert into T values=456 */ 1 row created. sys@XE> /*example comment*/ 1 row created. sys@XE> /* working comment because of the beginning with space character*/ sys@XE> –this is what a comment must begin with sys@XE> REM and again this is what a comment must begin with sys@XE> select * from t; A ———- 123 123 123 123 sys@XE>—you have 3 more rows and guess what will happen when you commit sys@XE> commit; Commit complete. sys@XE> select * from t; A ———- 123 123 123 123

This case is working for all statements you execute before the comment because the interpreter runs the previous command if you don’t have space after asterix. Woooow think about what this can cause for your commented batch operations

If I were you I would be careful before commenting and would use — instead of /* */

Now its time to read all off the Oracle Idiosyncrasies

About these ads