New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unit test regressions #1303
Comments
Looking at the upgrade script, we're going to get a 1075 error on this:
|
From http://dev.mysql.com/doc/refman/5.4/en/innodb-restrictions.html |
(In [2099]) fixes #1303 - quick fix until the Installer allows storage engine selection |
I'm not sure about this issue, as it works fine on my mysql: the idvisit is auto incremented separately for each idsite. The queries ran fine on the demo test database which is now running trunk. are there potential problems? |
The first Bamboo error is typical when the default storage engine is Innodb. Another scenario is when users try to convert their database from MyISAM to Innodb. The 1075 error in comment:1 occurs when updating a database that's already using the Innodb storage engine. |
ah! nice catch by bamboo there. I found a thread: http://www.mail-archive.com/mysql@lists.mysql.com/msg63181.html I think some users are using Innodb so it makes sense to try and stay compatible with this. The downside is an additional INDEX which will slow down tracker, but this is the only solution for now to have good performance in Live! widget. |
On r2098
Bamboo reporting:
Running unit tests locally:
The text was updated successfully, but these errors were encountered: