Hi BeeGee, My impression is that your first statement is correct, but not your second:
To use the query-cache with MySQL, you either need to use MyISAM tables, or if you use InnoDB tables and transactions, then you need to use at least MySQL version 4.1.1 This is not related to Django. -----Original Message----- From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Beegee Sent: vrijdag 21 april 2006 8:19 To: Django users Subject: Re: MySQL Query cache hits stay zero This is a part from the manual of MySQL: "In MySQL 4.0, the query cache is disabled within transactions (it does not return results). Beginning with MySQL 4.1.1, the query cache also works within transactions when using InnoDB tables (it uses the table version number to detect whether its contents are still current)." So, are the following statements correct? 1. Apparently all Django generated or MySQLdb generated statements are transactional. Even ordinary select statements? Because, only transactional statements are not cached. (Still, it is a bit strange because the value of Qcache_queries_in_cache does increase over time.) 2. To be able to use the query cache of MySQL when using MySQL as a backend database for Django, you need to use at least version 4.1.1. of MySQL. And you need to be using InnoDB tables. Berry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
