We have this issue atm:
A client gets his shop upgraded from CE 1.4 to CE 1.8. The file-upgrade went well, and the database upgrade went also well on our development machine.
When we try to upgrade the client's live-db on his live-machine (connect the 1.8-Magento to the database and open it in the browser), the process seems to run for a while and ends in a 500 error.
PHP error log is empty; as it's a shared host, we can not change the apache or mysql settings; the hoster, though "specialized im magento hosting", is unwilling to change the settings and tells me that I could finish the database-upgrade by repeatedly refreshing the browser-window when the 500 error occurs, because magento will then be upgraded in small steps. This might go on for hours.
My question now is:
- Is this true? I thought the sql-statements for database-upgrades would be wrapped in a transaction, so they could be rolled back if anything goes wrong.
- Could the answer provide a hint where I could look in the code to find the answer for this question?
Thanks for your time!