Block overrides and package upgrade

Permalink
I did some testing on how eCommerce works on 5.6 and while it seemed to work for most parts, I found following problem (not sure if it's about eCom itself or 5.6):

I had overriden the controller of product_list block but not any other files of the block. When I tried to upgrade the eCom package from 2.8 to 2.8.5, the update progress went halfway through and crashed with an error message stating that the necessary db.xml doesn't exist. So...is it an bug or a feature that if the controller of a block is overridden, the system tries to look for the db.xml from the override folder also?

Regardless of the failed upgrade, the package version number was "upgraded" 2.8.5 even though some parts of the upgrade didn't go through, like the addition of "product_description_auto" attribute. I solved the problem by copying the db.xml to /blocks/product_list/ and modifying the packages table via PhpMyAdmin to make the eCom version to "look" older and to be able to run the upgrade again.

 
Mnkras replied on at Permalink Reply
Mnkras
Yea, thats been an issue before 5.6, im not sure what the expected behavior for that should be.

Mike