> Is there a reason you are calling columns > before the query? If you can call it after running the query, the > columns will already be filled in, and won't require an additional > database query.
I'm calling columns first because I'm dynamically building queries and building html/csv from them, and in the output table the column headings come before the tbody. Some of the result sets are quite large, so I want to use #each rather than #all to output the rows, because I don't want to be loading the whole dataset in memory before starting to generate the output. I could possibly output the headings afterwards, and then do something downstream to re-arrange the output, but it seems cleaner to me to fix the issue I'm having at source. Like I say, I'll post something ready for general consumption soon (it could be that it might be better as an extension rather than part of the adapter though). Cheers, Roland -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
