Reading between the lines here... Are you saying that BLOCKFACTOR
doesn't affect the number of of rows returned in a query, it just
affects the interaction between the ODBC driver and CF? I'm not sure
that I have any idea then if designating the BLOCKFACTOR is either
necessary or benificial to any givent SP call.
Jim
-----Original Message-----
From: Bud <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, August 22, 2000 7:48 PM
Subject: Re: Stored Procedure BLOCKFACTOR
>On 8/22/00, Jim McAtee penned:
>>Could someone explain how the BLOCKFACTOR parameter of
CFSTOREDPROCEDURE
>>is used. It's not clear to me how the maximum number of rows returned
>>by a result set can be limited to 100 (according to the CF 4
>>documentation). What am I missing?
>
>Actually, from what I can deduct, ODBC passes the results from a
>query to CF one at a time. If you specify a blokckfactor, it will
>wait until it has that many results and then hand then pass them. So,
>if you return a query with 400 records, ODBC must talk to CF 400
>times. If the blockfactor is set at 100, they only "communicate" 4
>times, making the results return quicker.
>
>This is on a regular query. I presume it's similar with a stored
procedure.
>--
>
>Bud Schneehagen - Tropical Web Creations
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>ColdFusion Solutions / eCommerce Development
>[EMAIL PROTECTED]
>http://www.twcreations.com/
>954.721.3452
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
