Did you mean to blow the whole cache in memcached ? Do you know all the keys related to your result source stored there ? There might be a million keys.
2007/5/30, Brandon Black [EMAIL PROTECTED]:
The easiest approach is, of course, to cache aggressively (even ->search() based on serialized search args), and blow the whole cache on any ins/upd/del of anything in the table. This solves all consistency issues, but is far less than ideal efficiency-wise. -- Brandon _______________________________________________ List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class Wiki: http://dbix-class.shadowcatsystems.co.uk/ IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/ Searchable Archive: http://www.mail-archive.com/[email protected]/
_______________________________________________ List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class Wiki: http://dbix-class.shadowcatsystems.co.uk/ IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/ Searchable Archive: http://www.mail-archive.com/[email protected]/
