in reply to Re: SQL WHERE clauses with DBIx::Class, using NOT and IN in thread SQL WHERE clauses with DBIx::Class, using NOT and IN
This works well, thank you!
Interestingly, I have found that queries with large -in lists searching on the primary key, e.g. containing ~5000 elements, actually crash (ActiveState) perl. Where does this limit on the number of elements might come from?
Of course, I could break up the query and use a shorter IN condition; however, that would come at a severe performance penalty--the broken up queries use a total of 45 seconds. Also, the broken-up query is much slower than direct access to each row using the primary key: resultset('table')->find($pk)!
|