While working on the SQL stuff in the last blogpost, I had the problem, that my GROUP_CONCAT ignored my SEPARATOR ' ' and I had no clue why. What does one do in this moment? Ask the colleagues and the community.
Wrong:
GROUP_CONCAT(DISTINCT(o.sales_channel_id) SEPARATOR ' ')
Sorry for the german screenshot, but from time to time I’m lazy and prefer my mother tongue.
It is a screenshot from slack and I asked what the problem with my GROUP_CONCAT is, because the IDs are just merged together without any space in between. Björn Meyer mentioned Robin Homberg and he wrote, that it might be the problem, that GROUP_CONCAT doesn’t work well with binary fields and better explicitly run the id through HEX and it worked ?
Right:
GROUP_CONCAT(DISTINCT(HEX(o.sales_channel_id)) SEPARATOR ' ')The discussion ends with me telling Robin, that I’ll blog about it and mention him if it is ok – it was, so: Thanks Robin! And thanks Björn for telling him <3
You know the admin’s „duplicate“ button on products. Now the ticket says: „We need that, but from code — duplicate a product per sales channel, with adjusted name and its own product number.“ Or: „Campaign landing pages: clone this CMS page 20 times with different headlines.“ I’ve watched this get implemented as: load entity with […]
The requirement sounds harmless every time: „Log when a product price changes, with old and new value.“ Or: „When an order’s email changes, notify the old address.“ Or the audit-trail classic: „Who changed what, from what, to what?“ And every time, the naive implementation is the same sad shape: subscribe to product.written, load the entity […]
A code review scenario. A plugin adds a purchasePrice-style field to a custom entity — internal margin data. The review question: „Can the Store API read this?“ Followed by: „Can the Admin API write that computed field you recalculate in a subscriber?“ The answers, in the plugin at hand, were „yes“ and „yes, and then […]
