Noah,
Thanks for clarifying. Yes, I was using UTF-8 and definitely prefer to use the RPM version of MySQL on OpenSuSE. But its good to know there's a way around this.


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Noah White
Sent: Monday, October 23, 2006 2:48 PM
To: [email protected]
Subject: [Trac] Re: state of mysql support in 0.10

The default MYSQL build should support 1024 character length index fields, however, if you are running with a UTF-8 character set on your tables, then your chars will be 3 bytes wide so you need to take that into account. Alternatively you can recompile MYSQL with whatever character length index field you would like.

On 10/17/06, Richard Mixon <[EMAIL PROTECTED]> wrote:
Yes, would not go back. I did have trouble getting the indexes created, had to hand-jive them a bit - basically reduce the key-length on some text indexes. IIRC, MySQL does not support 1024 character length index fields, seems SQLite did.  Because of this, I'm a bit apprehensive about upgrading to he release 0.10 version, but do not expect it to be a real problem.
 
Also, I worked with a pre-release version of 0.10 from subversion.
 
Our use is relatively light (three users), but we use MySQL so extensively and have lots of tools for it. Going with SQLite just did not make sense.
 
Good luck


From: [email protected] [mailto:[email protected]] On Behalf Of John Joseph Bachir
Sent: Tuesday, October 17, 2006 12:49 PM
To: [email protected]
Subject: [Trac] state of mysql support in 0.10

Have folks had good experiences using mysql with 0.10? Is this bug a persistent (no pun intended) issue? http://trac.edgewall.org/ticket/3645





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to