Skip to content
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

[SQL] Missing explicit primary key definition in table log_profiling #287

Merged
merged 1 commit into from May 25, 2014
Merged

[SQL] Missing explicit primary key definition in table log_profiling #287

merged 1 commit into from May 25, 2014

Conversation

he667
Copy link
Contributor

@he667 he667 commented May 22, 2014

Missing explicit primary key definition in table log_profiling

@he667
Copy link
Contributor Author

he667 commented May 22, 2014

It doesn't bother mysql but other databases might not be as permissive.

mattab pushed a commit that referenced this pull request May 25, 2014
[SQL] Missing explicit primary key definition in table log_profiling

Cheers for pull request!
@mattab mattab merged commit 3e16d87 into matomo-org:master May 25, 2014
@sgiehl
Copy link
Member

sgiehl commented May 25, 2014

That one broke the build...

mattab added a commit that referenced this pull request May 25, 2014
it breaks the build Failed to setup fixture: TEST INITIALIZATION FAILED: SQLSTATE[42000]: Syntax error or access violation: 1170 BLOB/TEXT column 'query' used in key specification without a key length
@sgiehl
Copy link
Member

sgiehl commented May 25, 2014

And I'm not sure if that one made sense anyways. A unique key is not exactly the same as a primary key for sure but both don't make sense. And the definition file is not named 'MySQL.php' without a reason. The schema is for mysql only, other dbs would get another definition file.
And if we change the schema, we should ALWAYS also add an update script to keep all databases in sync.

@mattab
Copy link
Member

mattab commented May 25, 2014

sorry shouldn't have merged that one for these reasons

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants