Hi Berry, Beegee wrote: > My test results. I installed > mysql-standard-5.0.20-linux-x86_64-glibc23. Created a completely new > database and restored a backup from my 'old' django database into the > newly created MySql 5 instance. > > Restarted Apache and everthing was up and running again. Great! ..
I think a 'Whooot!' would be well placed here :) > So, it seems that the best thing to do to make use of the query cache > of MySQL is to use MySQL 5.0. > > I want to thank everybody for helping me. Great to hear all went great! But for reference, Query Cache is working since MySQL 4.0. I don't know what exactly happened here, but apparently the restriction of InnoDB within transactions not using Query Cache was the culprit, which was 'solved' in MySQL 4.1. Welcome to world of MySQL 5.0 ;) Btw, try to use the latest Python MySQLdb module, which has was recently being 'upgraded' to use more MySQL 5.0 stuff. Cheers, Geert -- Geert Vanderkelen http://www.some-abstract-type-shit.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
