I've worked at a company who produced a large banking application
(about 700 binaries and 200 dynamic libraries). We didn't have
much coding standards, but among the few we had was "you shall
never use 'select *'". Beside the problem mentioned that out
of order applying of patches can produce different order of
columns on tables, the other disadvantage of using 'select *'
is that it's a performance hit. It means that for each time the
query is compiled, the database has to do lookups and figure out
what the columns will be.
'select *' is just there for interactive usuage - applications
should never use them.
Abigail
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
