Changes between Version 39 and Version 40 of MySqlDb

Timestamp:

May 11, 2009, 9:14:50 PM (15 years ago)

Author:

Christian Boos

Comment:

move the #Conversion section up

MySqlDb

@@ -77 +77 @@
  - [http://mysql-python.svn.sourceforge.net/viewvc/mysql-python/tags/MySQLdb-1.2.2/MySQLdb/site.cfg?revision=499&view=raw MySQLdb-1.2.2/MySQLdb/site.cfg]
 
-== Known Issues ==
-=== Still Opened ===
-[[TicketQuery(keywords=~mysql&status=!closed&group=milestone)]]
-
-=== Typical Problems ===
-If you have some strange issues (typically `OperationalError: (2006, 'MySQL server has gone away')`, as in #3645, and your web frontend is Apache, you might have conflicting mysql libraries. Be sure to read: mod_wsgi:ApplicationIssues#MySQL_Shared_Library_Conflicts. Another possibility is that you've hit MySQL bug 36639, as explained in ticket:3645#comment:48.
-
-When changing collation to ''utf8'' MySQL may fail in 4.1.x and 5.0.x versions on MyISAM table type. It will complain about "too big" indexes in some Trac tables. This will be (hopefully) addressed in [milestone:0.10.4]. As a workaround it has been [comment:ticket:3659:5 recommended] to use InnoDB tables instead of MyISAM where this limitation is absent.
-
-[[TicketQuery(keywords=~mysql&resolution=worksforme)]]
-
-(corresponding [query:keywords=~mysql&status=!closed custom query])
-
-=== Troubleshooting ===
-If you get an error from python when using trac-admin like this:
-{{{
-OperationalError: (1045, "Access denied for user 'tracuser'@'localhost' (using password: YES)")
-}}}
-There are a few possibilities:
- 1. Try first to login on the command-line using the user tracuser (mysql -p -h localhost -u tracuser)
- 1. Created user is not yet used by MySQL (Login to the MySQL server(as root): mysql -p and type FLUSH PRIVILEGES;)
- 1. The user is added but the host does not match in the mysql user table (I had this on my FreeBSD setup). mysql -p; use mysql; UPDATE user SET Host="localhost" WHERE User="tracuser"; FLUSH PRIVILEGES;)
-
-
-== Conversion ==
+== Conversion Procedures == #Conversion
 
 ==== MyISAM to InnoDB ====
@@ -127 +103 @@
 ==== From SQLite ====
 Users have reported success with the [wiki:SqLiteToMySql following method].
+
+
+== Known Issues ==
+=== Still Opened ===
+[[TicketQuery(keywords=~mysql&status=!closed&group=milestone)]]
+
+=== Typical Problems ===
+If you have some strange issues (typically `OperationalError: (2006, 'MySQL server has gone away')`, as in #3645, and your web frontend is Apache, you might have conflicting mysql libraries. Be sure to read: mod_wsgi:ApplicationIssues#MySQL_Shared_Library_Conflicts. Another possibility is that you've hit MySQL bug 36639, as explained in ticket:3645#comment:48.
+
+When changing collation to ''utf8'' MySQL may fail in 4.1.x and 5.0.x versions on MyISAM table type. It will complain about "too big" indexes in some Trac tables. This will be (hopefully) addressed in [milestone:0.10.4]. As a workaround it has been [comment:ticket:3659:5 recommended] to use InnoDB tables instead of MyISAM where this limitation is absent.
+
+[[TicketQuery(keywords=~mysql&resolution=worksforme)]]
+
+(corresponding [query:keywords=~mysql&status=!closed custom query])
+
+=== Troubleshooting ===
+If you get an error from python when using trac-admin like this:
+{{{
+OperationalError: (1045, "Access denied for user 'tracuser'@'localhost' (using password: YES)")
+}}}
+There are a few possibilities:
+ 1. Try first to login on the command-line using the user tracuser (mysql -p -h localhost -u tracuser)
+ 1. Created user is not yet used by MySQL (Login to the MySQL server(as root): mysql -p and type FLUSH PRIVILEGES;)
+ 1. The user is added but the host does not match in the mysql user table (I had this on my FreeBSD setup). mysql -p; use mysql; UPDATE user SET Host="localhost" WHERE User="tracuser"; FLUSH PRIVILEGES;)