I don't believe that's entirely correct.. had this issue one 1 server while the others had the old SQL::Statement with no issue even though they update every night.. The problem was fixinterchange script or changing from 4.8 to 4.9 version. I had reverted it back to the old version and it did not overwrite till 2 days ago with Cpanel6Originally posted by Nico
Yes, as I found out running /scripts/fixinterchange, /scripts/upcp and the nightly updates will put you back to square one again. I disabled the cron for the nightly updates for now. Cpanel support advised me of the following:
"It appears to be fairly large (and common) problem (search google.com), the SQL::statment module no longer includes the 'where' function, and it is upgraded via the bundle::interchange package from cpan nightly. Our developers are currently working on a fix for this and should have one within a couple of days."
Once they get it squared away I will enable the updates once again.
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
T | Interchange & postgresql | Databases | 0 | |
P | Interchange SQL::Statement Errors | Databases | 2 | |
K | interchange and my sql problems | Databases | 0 | |
![]() |
Interchange and mysql | Databases | 2 | |
C | Interchange and MySQL | Databases | 0 |