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

Jump to bottom

Piwik uses MySQL reserved word 'option' for table name #444

Closed
anonymous-matomo-user opened this issue Nov 27, 2008 · 2 comments
Closed

Piwik uses MySQL reserved word 'option' for table name #444

anonymous-matomo-user opened this issue Nov 27, 2008 · 2 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority.
Milestone
RobotRock

Comments

@anonymous-matomo-user
Copy link

While attempting to upgrade 0.2.9 to 0.2.24, I’m finding MySQL unable to handle the upgrade.

It would appear that some parts of the upgrade process fail because the table ‘option’ is a MySQL reserved word (see http://dev.mysql.com/doc/refman/5.0/en/reserved-words.html) and it is not escaped correctly. The upgrade process has the following error:

```
Error trying to create the option table in Mysql: SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘option’ already exists
```

But this would appear to be a by-product of something else wrong (attempting to delete the table? Not sure yet)

Please note that this broken upgrade appears to have more or less completely botched my installation and it would be worthwhile to put a warning for people downloading this version that it’s a problem.
@anonymous-matomo-user
Copy link
Author

Please also note that installing 0.2.24 without a table prefix will result in the first page after installation stating that a database upgrade is available, which will of course fail.

@mattab
Copy link
Member

mattab commented Nov 27, 2008

this should be fixed in 777 Please try release 0.2.25 (to be released)

@anonymous-matomo-user anonymous-matomo-user added this to the RobotRock milestone Jul 8, 2014
@newmediamadman newmediamadman mentioned this issue Oct 6, 2020
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority.
Projects
None yet
Milestone
RobotRock
Development

No branches or pull requests
2 participants
@mattab @anonymous-matomo-user