Tally List : mailing list management, archiving, and analysis
click for archive home
 
Archive of:
CF-Talk
Cold Fusion - Technical
 
home
24 hour view
quick stats
weekly updates
 
all tallylists
corporate solutions
archive your favorite
help / feedback


Search the Tallylist search by keyword:

About Cold Fusion :
product's home
product's list home
 
  Archived TallyList / CF-Talk: 
Subject: RE: SELECT * Queries
Raymond B. (82p/+0r)     Posted: Saturday 31 Mar 2001
This post: 152 views, +0 rating

The warning about wildcards (*) is due to users wanting specific fields yet returning a whole record b/c it's easier to type (which is a huge waste). If you truely do want every piece of information (and will continue to do so in the future ie. even if fields are added) then by all means that's what a wildcard is for. One thing to consider with large queries is the overhead of transmitting the statement itself, if you're getting a small record set with many fields (or a single record) your sql statement can be almost as large as the returned set. This is where stored procedures come in, Access doesn't support them but you can store the query server side and use it's views to mimic very basic sps. I never use Access if I have any choice in the matter, so for the exact syntax to do so you might want to check SWYNK out (http://www.swynk.com) whenver you have to do anything even remotely related to M$ it's a great place to start, so is MSDN (http://msdn.microsoft.com). Even with small queries executed thousands of times daily the transmission of the query can account for a large part of traffice. Without going into a lot of detail, other DBMSs (I use the term loosely in regards to Access ;) with varying degrees of sp support will also optimise/compile the query for added performance benefit.

-----Original Message----- From: Bud [mailto:webcreation@mindspring.com] Sent: March 31, 2001 07:07 To: CF-Talk Subject: RE: SELECT * Queries

On 3/31/01, Jonathan Lim penned: >Hi Bud, > >My DBA told me that the * will mean more data has to be transferred from the >DB server to your CF server. That's what slows it down. The DB time spent >getting the data for * or for a specific field is negligable. We're working >with DB2.

I understand that if I only needed data for 10 out of 100 fields, then yes it would be quicker to name the fields. But what about when I need the entire record? I read from someone on here that CF had to do an extra call to the database or something. Like once to get the field names and then to query it.

In answer to Luke, I'm using Access on this little app I'm building. --

Bud Schneehagen - Tropical Web Creations

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ ColdFusion Solutions / eCommerce Development buddy@twcreations.com http://www.twcreations.com/ 954.721.3452


Similar Subject Line Posts (+/- two weeks of this post)
RE: SELECT * Queries  02 Apr 2001   (48 v/ +0 r)
RE: SELECT * Queries  31 Mar 2001 (this post)   (152 v/ +0 r)
RE: SELECT * Queries  31 Mar 2001   (53 v/ +0 r)
RE: SELECT * Queries  31 Mar 2001   (64 v/ +0 r)
RE: SELECT * Queries  31 Mar 2001   (49 v/ +0 r)
RE: SELECT * Queries  31 Mar 2001   (37 v/ +0 r)
Re: SELECT * Queries  31 Mar 2001   (37 v/ +0 r)
SELECT * Queries  31 Mar 2001   (58 v/ +0 r)
 

Send a reply to the CF-Talk list!
click to send a reply! NOTE: Many lists will reject your post unless you have already registered with them. Also - don't forget the right account to send from (for those with multiple emails!)

Feedback: If this post was exceptionally helpful, please help by giving this post a positive review.

 

TallyList : copyright Ububik - 2000