Comments on: How to hurt your brain with Oracle http://www.magpiebrain.com/blog/2004/01/28/how-to-hurt-your-brain-with-oracle/ Sam Newman's blog Sun, 12 Oct 2008 07:24:59 +0000 http://wordpress.org/?v=2.5.1 By: Sam Newman http://www.magpiebrain.com/blog/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-164 Sam Newman Thu, 29 Jan 2004 10:46:21 +0000 http://www.magpiebrain.com/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-164 Yeah - I use a prefix as well having been bitten by that particular bug a couple of times in my early Java days. Checkstyle and PMD should also pick it up as a usless statement too. The annoying thing with the Oracle bug was that I completely forgot that SQL is case insensitive.... Yeah – I use a prefix as well having been bitten by that particular bug a couple of times in my early Java days. Checkstyle and PMD should also pick it up as a usless statement too. The annoying thing with the Oracle bug was that I completely forgot that SQL is case insensitive….

]]> By: JM Ibanez http://www.magpiebrain.com/blog/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-163 JM Ibanez Wed, 28 Jan 2004 23:07:42 +0000 http://www.magpiebrain.com/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-163 I usually avoid such issues by prefixing parameter variables with 'p_'; that way, I know which variable I'm referring to. (And I don't have to worry about case insensitivity either) I usually avoid such issues by prefixing parameter variables with ‘p_’; that way, I know which variable I’m referring to. (And I don’t have to worry about case insensitivity either)

]]> By: Behrang http://www.magpiebrain.com/blog/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-162 Behrang Wed, 28 Jan 2004 19:41:55 +0000 http://www.magpiebrain.com/2004/01/28/how-to-hurt-your-brain-with-oracle/#comment-162 Hi The same also happens in Java: class X { int a; public void method(int a) { a = a; } } The above class compiles with no problems but does not do what it was meant to do. The a = a has to change to this.a = a to work correctly. The compiler does not give any errors but some IDEs such as Eclipse underline that statement saying it does not have any effect on the variable a... Hi

The same also happens in Java:

class X {

int a;

public void method(int a) {
a = a;
}
}

The above class compiles with no problems but does not do what it was meant to do. The

a = a

has to change to

this.a = a

to work correctly. The compiler does not give any errors but some IDEs such as Eclipse underline that statement saying it does not have any effect on the variable a…

]]>