DiecastX

I would absolutely recommend you wait til 3.0.4 to see if it fixes the RTE issues. Since 3.0.1 we have had major compatibility issues. I wouldn't recommend you go to 3.0.3.

I agree, it would be nice if the software had some basic password selection enforcement, such as not allowing use of your username as your password as suggested above. Another would be not allowing single dictionary words. A settable minimum password length is another good one. Ultimately some sort of "meter" that shows your password strength, with suggestions on how to choose a good password would be ideal.

..Al

I like it! When will 3.0.4 be released? kidding, kidding...

Okay, waiting for feedback on this release. 3.0.2 was such a dog, this has got to be an improvement...

Interestingly, mysqltuner and tuning-primer conflict on join_buffer_size. I am at 6M now, mysqltuner is telling me to increase, tuning-primer is telling me to decrease. Ideas?

mysqltuner is telling me, among other things, this:

Adjust your join queries to always utilize indexes

Does anyone know what I should do about it?

Disregard. Resolved.

Is it okay to use values such as, say, 48MB? Instead of doubling from 32M to 64M, is it okay to use a 50% increase?


Extremely appreciative of this thread!