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

Use of reserved word "value" as a table and column name #1437

Merged
merged 2 commits into from
Aug 13, 2019

Conversation

julia-bauder
Copy link
Contributor

"Value" is a reserved word in some versions of MySQL/MariaDB. If you're using one of those versions, queries that access or modify the "value" table currently fail with a syntax error. Escaping "value" as a table and column name fixes the error for people running one of those versions, and should not affect usage by people not running one of those versions.

"Value" is a reserved word in some versions of MySQL/MariaDB. If you're using one of those versions, queries that access or modify the "value" table currently fail. Escaping "value" as a table and column name fixes the error for people running one of those versions, and should not affect usage by people not running one of those versions.
@zerocrates
Copy link
Member

Can you clarify the versions you've had problems with, if any?

Or perhaps it's some other setting and not the version at issue? We've run S on a decent variety of versions of both MySQL and Maria and haven't encountered this as an issue.

@julia-bauder
Copy link
Contributor Author

10.4.7-MariaDB

@zerocrates
Copy link
Member

We've had another report of this problem, with the same version... it's still a little curious as I can't find any mention in the documentation or release notes of 10.4 changing the handling of VALUE as reserved. I'm left thinking it's one of: a purposeful change that was undocumented, something else like a changed SQL_MODE (this is reported in the Omeka S system information page), or it's a bug in 10.4.

Anyway, we can quote the usage of value as you suggest without issues, but it's just curious. And given we've had 2 reports now close in time to each other after none to this point, it suggests something that was a recent-ish change.

@zerocrates zerocrates merged commit 3fdf5ee into omeka:develop Aug 13, 2019
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.

2 participants