Charlie,
No pushing of buttons going on, I was asking like a lemming because I
was wondering if there were other reasons that I did not know about. I
am aware of the larger amounts of data where unneccessary, but thats
about it.
Sometimes I find asking this way on a list questions like these
I am a SELECT * user.
(In my defence, I'm self-taught and didn't know any better until now)
My question... is there a trick or tip or tool that you guys use to save
typing in the name of every field that you're after? If you're populating
a big long form, it's a real pain to type every field
Hi Tom,
If you're doing SELECT * for a single record then don't worry about it - the
overhead is minuscule. The real problems with SELECT * happen when you are
running a query that will return multiple (hundreds/thousands of) records and
the overhead can become enormous. And if you are doing
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Why select * is bad (was RE: [cfaussie] Re: @#$!!
Queryparam)
I am a SELECT * user.
(In my defence, I'm self-taught and didn't know any better until now)
My question... is there a trick or tip or tool that you guys use to save
typing
, and I'm a Select * user. :-)
/Charlie
http://www.carehart.org/blog/
_
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Tom MacKean
Sent: Monday, March 05, 2007 7:48 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Why select * is bad (was RE: [cfaussie] Re
://www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
*From:* cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED]
*On Behalf Of *Tom MacKean
*Sent:* Tuesday, 6 March 2007 11:48 AM
*To:* cfaussie@googlegroups.com
*Subject:* [cfaussie] Re: Why select * is bad (was RE: [cfaussie] Re
*To:* cfaussie@googlegroups.com
*Subject:* [cfaussie] Re: Why select * is bad (was RE: [cfaussie] Re:
@#$!! Queryparam)
I am a SELECT * user.
(In my defence, I'm self-taught and didn't know any better until now)
My question... is there a trick or tip or tool that you guys use to save
typing
Of Tom MacKean
Sent: Monday, March 05, 2007 7:48 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: Why select * is bad (was RE: [cfaussie] Re: @#$!!
Queryparam)
I am a SELECT * user.
(In my defence, I'm self-taught and didn't know any better until now)
My question
@googlegroups.com
Subject: [cfaussie] Re: Why select * is bad (was RE:
[cfaussie] Re:
@#$!! Queryparam)
Thanks Charlie,
I'm alternating between Dreamweaver and Eclipse
at the
moment, depending on the project. Since my original post, I found a
button in
MySQL Manager
I have seen 2 notable reasons to stay away from select * if possible:
1. I have come across several issues with the schema changing in a
database and the changes where not reflected in a query that had select *
(legacy code). This can make the display layer break in strange ways when
10 matches
Mail list logo
