it looks way better now for me. it is long but it's kinda ok for a blue kata. the idea of task is somewhat complicated per se (looks like a normal request from normal manager), so I see no good way to shorten it without loosing some sense.

I cannot remember how exactly bad it was but it definitely was much worse, I remember I had to read it several times even before pressing 'train', not after I found I wrote smth wrong as usual

P.S. feel free to reach me at discord as well if needed

it's ok, I can approve the kata once this kata is ready for approval, even with my current solution invaldited :)

Done ;-)

LOL you have summoned me (technically speaking ? XDD) . I had indeed find my "date", but it's not the one you're thinking about.😏 Anyhow, thanks for reminding me about this kata, I will make some changes and publish it tommorrow (need some rest now ^^

Thanks! Glad you liked it. Cheers :)

Any suggestions on improvements? (Or do you have a kata of yours as an example) ??

The median vote was 2 kyu, so don't worry about it. And it's good to finally see a purple SQL kata.

Haven't expected it happens soon : ) Thanks for approving. Cheers!

I'm bad at estimating :) It supposed to be a blue kata, so I've put some number

ok :)

maybe you could add some amount of data to timeout such solutions :-)
But I'm not sure whether it is possible with current description and schema without timing out other approaches

oh, yes. started solving before you've changed. with money everything is better :)

it depends on column names. in most kata they are not convenient enough to use natural join :)
but sometimes I use it when possible

keep those kata's coming

This one ignores the "ordered by product ID in descending order" part, the order happens to be correct. The other solution should be correct.