<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by AJ
»
Preventing usage of "SELECT *..."
141 posts, Page 1 of 15
1
2
3
4
5
»
»»
Preventing usage of "SELECT *..."
Rate Topic
Display Mode
Topic Options
Author
Message
Raghuram (AJ)
Raghuram (AJ)
Posted Wednesday, November 04, 2009 9:44 PM
SSC-Addicted
Group: General Forum Members
Last Login: Friday, June 15, 2012 7:53 PM
Points: 494,
Visits: 299
Comments posted to this topic are about the item
Preventing usage of "SELECT *..."
The vision must be followed by the venture. It is not enough to stare up the steps - we must step up the stairs.
- Vance Havner
Post #813982
ChiragNS
ChiragNS
Posted Thursday, November 05, 2009 2:59 AM
SSCrazy
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365,
Visits: 1,825
Interesting but i feel its not practical to add dummy columns to tables.
"Keep Trying"
Post #814090
Scott.Deagan
Scott.Deagan
Posted Thursday, November 05, 2009 3:55 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, November 05, 2009 3:53 AM
Points: 1,
Visits: 0
Another solution that works well in most situations is to simply avoid allowing users to execute SQL statements at all - ensure that all access to tables is performed via stored procedures.
Post #814103
gary-915906
gary-915906
Posted Thursday, November 05, 2009 4:01 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, April 09, 2010 8:36 AM
Points: 2,
Visits: 23
We have similiar issues here with the use of *, espically with young developers.
As all our DB projects are under source control, ive been able to control checking in SQL containing * using Code Analysis and Check in policies.
Regards
Gary Howlett
www.garyhowlett.co.uk
Post #814107
Vishal Singh
Vishal Singh
Posted Thursday, November 05, 2009 4:25 AM
Old Hand
Group: General Forum Members
Last Login: Wednesday, February 13, 2013 12:30 AM
Points: 353,
Visits: 487
Indeed a good article but practically difficult to use.
-Forum Etiquette: How to post Performance Problems
-Forum Etiquette: How to post data/code to get the best help
Post #814115
Jason-299789
Jason-299789
Posted Thursday, November 05, 2009 4:30 AM
SSC Eights!
Group: General Forum Members
Last Login: Today @ 10:31 AM
Points: 836,
Visits: 2,192
In interesting solution, for a not so real problem, as any decent organisation has standards in place and will ensure that all code conforms to the corporate standards.
If not the developer resonsible needs to rewrite the code in line with the standards, they eventually learn that they cant write Selcet * as they have to do double the work.
Besides with the 2008 GDR, you can enforce these at a code entry level.
_________________________________________________________________________
SSC Guide to Posting and Best Practices
Post #814119
John Muir
John Muir
Posted Thursday, November 05, 2009 5:14 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, March 17, 2011 4:53 AM
Points: 4,
Visits: 51
I think you can still use 'select anyfield, tblname.* from tblname' though.
Post #814135
Michael Lysons
Michael Lysons
Posted Thursday, November 05, 2009 5:16 AM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 4:05 AM
Points: 1,127,
Visits: 937
I love posts like this. Sure, the specific example used may not be practical, but I just like the thinking behind coming up with the solution. Often that in itself can open up other avenues of thought that would otherwise have remained hidden.
Post #814141
Ponte
Ponte
Posted Thursday, November 05, 2009 5:30 AM
SSC Rookie
Group: General Forum Members
Last Login: Tuesday, June 07, 2011 8:13 AM
Points: 42,
Visits: 54
May not be practical.
May not be standard.
But it is a good/smart solution.
Regards.
Fernando Ponte
factdata.com.br
Post #814153
John Muir
John Muir
Posted Thursday, November 05, 2009 5:41 AM
Forum Newbie
Group: General Forum Members
Last Login: Thursday, March 17, 2011 4:53 AM
Points: 4,
Visits: 51
But it does not solve the problem when I can use
select tblname.* from tblname
with the same result.
Post #814162
« Prev Topic
|
Next Topic »
141 posts, Page 1 of 15
1
2
3
4
5
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
