I've made changes in the trunk for 0.3.9 that I hope will take care
of reflection issues reported in MySQL 3.23, 4.0 and 4.1, as well
as odds and ends in current releases. It would be super super
useful if anyone who has had reflection issues in the past to pull
a copy of the trunk and give
I just tested this on MySQL 4.0.20c and it seems to have solved the
autoload problem.
What is the timeframe for cutting the 0.3.9 release?
Brian
On Jul 12, 1:00 pm, jason kirtland [EMAIL PROTECTED] wrote:
I've made changes in the trunk for 0.3.9 that I hope will take care
of reflection
bbull wrote:
I just tested this on MySQL 4.0.20c and it seems to have solved
the autoload problem.
Great. Thank you!
What is the timeframe for cutting the 0.3.9 release?
Very soon, probably in the next couple of days.
-j
--~--~-~--~~~---~--~~
You
I've run into this problem as well when working with MySQL 4.0.20c. I
believe the code needs to read:
decode_from = connection.execute(show variables like
'character_set').fetchone()[0]
When issuing that sql at the command prompt, i get back the following:
mysql show variables like