Changes between Version 1 and Version 2 of Ticket #40655, comment 4
- Timestamp:
- 09/01/2017 09:39:51 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #40655, comment 4
v1 v2 4 4 I don't mind making the `"Table Prefix" is invalid` message more friendly, but that's not the issue here, `wp_` is a perfectly valid prefix. 5 5 6 The check added in [37581] is supposed to disallow prefixes like `7e1_` that could be parsed as a value. This appears to work as expected, but in some cases it triggers the `Unknown column 'wp_' in 'field list' for query SELECT wp_` message, which should be silently discarded, not displayed to the user.6 The check added in [37581] is supposed to disallow prefixes like `7e1_` that could be parsed as a value. This appears to work as expected, but in some cases it triggers the `Unknown column 'wp_' in 'field list' for query SELECT wp_` error, which should be silently discarded, not displayed to the user.