New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance is better when fetching all rows at once #4539
Conversation
…or upgrade from < 1.5.2.0
[-] BO : Notice in AdminCustomers
…ooks [-] FO : Added missing hook for AdvancedEU on accessories
[*] TR: update Swedish installer
The $period var was not taken into account in the SQL.
[-] CORE : cleanCompareProducts interval
[-] CORE : Fix #PSCSX-7012, bad length for compagny field (address) for upgrade from < 1.5.2.0
[-] IN: Wrong id_guest in cart.xml
[-] FO : Fix undefined var when no combinations
[*] FO: theme.sql new demo address
[-] BO : Fix #PSCSX-7050, wrong pictures shown in AdminProducts
[-] FO : Fix performances issue with SpecificPrice (PSCSX-6942)
//Fix d81b70a - category must be an object, not an array
…e-select // HELPER: Add brackets to multiple select name field
…ad of full products list
[*] CORE : SpecificPriceRule without conditions to id_product 0 instead of full products list
[*] BO : Add versioning to addJS to renew admin.js
This commit 82c9dea introduce a bug, the parameter passed to the function was ignored and the table was cleaned all entries older than a week Since the function have been working this way for 4 years, we decided to not change the behavior and remove the parameter.
[*] BO : #PSCFV-12359 #PSCSX-1257 product tab async loading
…ductClearCache // CORE: Only clean compare_product table if entry older than 1 week
// update_eu_taxrulegroups.php avoid fatal in travis (php56)
[+] Check PHP syntax error with travis
[-] FO : Fix wrong date check in specific price
…ting over the result
Hey @studiokiwik, thank you for remaking this PR on the Also, could you follow these title guidelines? http://doc.prestashop.com/display/PS16/How+to+write+a+commit+message Thank you! |
Hi, Please update your PR and I'll merge it right away. Otherwise I'll have to cherry-pick your commit but the PR won't appear as merged. :( |
@julienbourdeau, the commit itself is 2480e5d, do you think it's mergeable easily? No risk of side-effect? |
Yeah it seems good to me and many peolple here #4368 :) |
Alright! Hey @studiokiwik, please update or remake your PR so you can get proper credit within the Git history :) |
Hey @mickaelandrieu, can you cherry-pick this one? Thanks! Keeping it open until you have created your own PR. |
Moved from #4368