Feeling Lucky
?
[#13854] - Fix sql error for Smart Search: Content Maps on postgresql
- Fixed in Code Base
- 15 Feb 2017
- Medium
- Build: staging
- # 13854
- Diff
- csthomas:pgsqlfix
User tests: Successful: Unsuccessful:
Pull Request for Issue #13848 point 2.
Summary of Changes
Redesign sql query which should now work on postresql and mysql.
(on mssql start to work after you apply PR #13895)
Create it in a simple and in more readable way.
Testing Instructions
- Install or use installed joomla staging with sample data
- Go to backend component Smart Search: Indexed Content
- Enable a plugin mentioned in page if disabled and create index if missing.
- Go to Content Maps (on mysql it works, on postgresql you get error)
- you should set up limit of displayed items to bigger number than 50 to see all items.
- Open a new browser tab and apply current PR.
- Go back to Content Maps:
- on mysql it should still works in the same way (you can compare results with previous browser tab)
- on postgresql it start working
Expected result
Page administrator/index.php?option=com_finder&view=maps works on postgresql.
Actual result
Joomla on postgresql generates errors.
Documentation Changes Required
No
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_finder |
| Labels |
Added:
?
|
||
| Title |
|
||||||
C-Lodder
- comment
- 10 Feb 2017
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13854.
csthomas
- comment
- 10 Feb 2017
Yes, because it was designed for postgresql and mssql for j3.7.
In general it should work and look better for all db.
waader
- comment
- 14 Feb 2017
I have tested this item
Thanks!
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/13854.
wilsonge
- | Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-02-15 12:40:12 |
| Closed_By | ⇒ | wilsonge |
Working fine on J4, but you seemed to have pushed this to the staging branch