Comments on: Column qualification best practice

By: Laurent Schneider

Laurent Schneider — Fri, 08 Jun 2007 20:19:22 +0000

yes, I agree… bad example , but in principleit is ok to use * with records

By: Patrick Wolf

Patrick Wolf — Fri, 08 Jun 2007 16:32:41 +0000

For records SELECT * could be ok, but your example wouldn’t be a good one where I personally would use a record

Because it just uses two attributes of that record. Waste of resources, especially if you consider you have some long VARCHAR2 columns in your table…

Patrick

By: Laurent Schneider

Laurent Schneider — Fri, 08 Jun 2007 08:47:45 +0000

> “select *” should be banned from all production code.

maybe with records it is ok

declare r emp%ROWTYPE; 
begin 
  select * into r
    from emp
    where ename='SCOTT';
  update emp
    set sal=r.sal+100 
    where empno=r.empno;
end;
/

By: Oracle Musings » Column Naming

Oracle Musings » Column Naming — Thu, 07 Jun 2007 13:11:33 +0000

[...] Laurent’s post on column qualification reminded me of a conversation I had with one of my staff about column naming standards. But before I get to that conversation, I’d like to share my favorite example about using table aliases. [...]

By: Beth

Beth — Thu, 07 Jun 2007 03:09:56 +0000

I wholeheartedly agree! “select *” should be banned from all production code. Period.

This was one of many “being a professional developer” lessons drummed into my brain by the senior dba at my first real database job. I remember thinking it was rather silly, until I lived through the first dot release of the product. Suddenly it all made sense….

By: Marco Gralike

Marco Gralike — Wed, 06 Jun 2007 15:49:11 +0000

The use of aliases should be mandatory…(diminishes a lot of code errors)