On Tue, Jul 15, 2014 at 2:23 PM, Olemis Lang <[email protected]> wrote:
> On Tue, Jul 15, 2014 at 2:08 PM, Morgan Tocker <[email protected]> > wrote: > > > > > On Jul 14, 2014, at 4:32 PM, Olemis Lang <[email protected]> wrote: > > > > >> If I choose MySQL, What is the advantage/disadvantage? > > >> > > >> > > > ... well ... at least I've tested it and deployed it using postgresql , > > > never with MySQL . > > > > I'm more of a lurker on this list... > > > > But MySQL should be a great fit for the query workload I would expect > from > > bloodhound. > > > > If you experience problems to the contrary, I'd be happy to provide > > suggestions. > > > > > Well , before I just shared my experience . It'd be really nice to improve > MySQL support and systematically test BH core with MySQL as a backend . > > -- > Regards, > > Olemis - @olemislc > Previously MySQL support in Trac has not been as good as PostgreSQL support. However, as far as I can tell MySQL support is pretty good in Trac 1.0.1, on which Bloodhound is based. The most common issue that users encounter is not creating tables with InnoDB or NDB type, utf8 character set and utf8_bin collation. So pay careful attention to the steps (1). These requirements will be enforced in Trac 1.0.2 (2). I think we have some instructions on the Bloodhound wiki specific for MySQL, but it seems the site is unreachable at the moment. (1) http://trac.edgewall.org/wiki/MySqlDb (2) http://trac.edgewall.org/ticket/10993
