> > > I assume this means you don't set BLOCKFACTOR in those cases
> > > where doing so would slow CF down. (That is, those cases where
> > > the data returned exceeds 32K.)
> >
> > There's nothing wrong with using BLOCKFACTOR when you're
> > returning datasets larger than 32Kb. In fact, that's the best
> > time to use it. What you don't want to do, according to the
> > folks at Allaire, is use a value for BLOCKFACTOR which would
> > end up being larger than 32Kb. So, you find out the maximum
> > length of a single row in Kb, and divide that into 32Kb.
>
> I think/hope we're saying the same thing.
>
> Re-writing your sentence below to state it to my understanding:
>
> "What you don't want to do, according to the folks at Allaire,
> is use a value for BLOCKFACTOR, where BLOCKFACTOR multiplied by
> the row size exceeds 32Kb."
I'm not sure if we're saying the same thing or not. Looks to me like your
chad is hanging.
Seriously, though, what I'm saying is that you don't want to set the
BLOCKFACTOR attribute to a value higher than the maximum length of a single
row, divided into 32Kb. That's almost always going to give you a value
greater than 1, however, so you'd get some value out of setting it to the
appropriate size.
> I also thought BLOCKFACTOR had a maximum value of 100.
So I've been told, although I haven't checked for myself. It's relatively
rare that you'd be able to set it this high, anyway - you'd need pretty
short rows for that.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
