SHOW TABLES LIKE is not PostgreSQL compatible
| Project: | Boost |
| Version: | 6.x-1.x-dev |
| Component: | Cron Crawler |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Hi there,
I noticed today that I was getting many errors on one of my sites. Now why on that site and not others... I'm not too sure, but the fact is that the SHOW TABLES LIKE is MySQL specific and thus you cannot use it just like that. (See #286986: MySQL: SHOW TABLES LIKE database.tablename doesn't work for a solution)
To the minimum you'd need to make boost_get_time() return 0 if someone uses PostgreSQL. Meaning that the whole CRON feature is not available for people like me. (No big deal, if you ask me!)
So at this time I just turn off that feature and the error goes away, except in the boost_block() which may generate that error too.
By the way, I would suggest you check for installed (enabled) modules rather than the database for a table. This would be more likely to work properly in all cases.
Thank you.
Alexis
P.S. as a side note, if you do not check for "history", you may want to remove the variable from the max() call below. (line 2054 and 2061 in the Oct 24th version.)

#1
Thanks, let me know if this does it. Checking for the table makes life easy; otherwise I have to check for the module, figure out what module uses what table and then check for that table.
#2
committed
#3
Automatically closed -- issue fixed for 2 weeks with no activity.