I often use sqlite for these kind of purposes. Works like a charm. On Mon, Oct 24, 2011 at 10:48 AM, Matija Grabnar <[email protected]>wrote:
> You have another possibility: create the temporary tables in another > database. This database can be on your OWN server, so the HUGE company > doesn't even have to know about it. > > If you were to download the full resultset and do the searching in Perl you > would in effect be doing the > same thing, except your database would be in your RAM, and you would be > using Perl instead of SQL > to search for it. For large datasets (which this seems to be) a database on > the local server is more efficient than doing it all in RAM. > > > ______________________________**_________________ > List: > http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/dbix-**class<http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class> > IRC: irc.perl.org#dbix-class > SVN: > http://dev.catalyst.perl.org/**repos/bast/DBIx-Class/<http://dev.catalyst.perl.org/repos/bast/DBIx-Class/> > Searchable Archive: http://www.grokbase.com/group/** > [email protected]<http://www.grokbase.com/group/[email protected]> >
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
