[EMAIL PROTECTED] wrote: > > The "order by" clause I think is what causes the memory allocation of > "aType" for each row.
I think you are right. The aType is cached when data is coming out of the database file so the allocation only occurs once. But when data is coming out of the sorter, the aType must be reallocated and recomputed each type a column of the result set is referenced. This needs to be worked on.
> > This does point out however, that Win32 users who need to use ORDER > BY on a large table are paying a hefty price. >
Win32 users pay a hefty price for lots of thing ;-)
-- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
