Thanks Ted & Stephen, I'll try out those strategies and see how it goes..
At 01:27 PM 11/21/2008, you wrote: >On Fri, Nov 21, 2008 at 11:53 AM, Steve Ellenoff ><[EMAIL PROTECTED]> wrote: > > > > Another idea I had was to write to a temp table on the backend the > > records the user selected and then select from the temp table and > > original table to get the final result. What I don't like about this > > idea is having to send possibly 3000 insert statements if the user > > wants to include 3000 records in the report. That sounds like it'd be > > terribly slow. > >That is exactly how I have done it in the past. Performance is >unlikely to be slow; you're creating a temp table with a single column >of integer keys, and I'd do some timing checks before even considering >optimizing at all. If need be, you could do some sort of a bulk insert >(there are a couple of options), wrap in a single transaction, etc. >but I think you'd find straight SQL Inserts to be fast enough. The >temp table will like just be a transient in-memory table, so for a >sufficiently-scaled back-end server, this shouldn't be a real problem. > > >-- >Ted Roche >Ted Roche & Associates, LLC >http://www.tedroche.com > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
