Will you do maintenance on kata's with language-specific blocks in the description? .. right, I didn't think so. Feel free to add a suggestion, go to GitHub or Discord to make your case.
I don't like that there's a column named id and no mention of it. It disables the solution starting with SELECT love.*,.
As a general remark, adding SQL-specific requirements as a comment in the solution template is a practice with poor usability. I suggest Codewars let translations (as well as original kata statements) consist of the universal part and a language-specific one.
Boss!
very nice
This comment is hidden because it contains spoiler information about the solution
There is always solution beyond my imagination!
Don't mark "Issue" for stating your personal preferences, use "Suggestion" instead.
Will you do maintenance on kata's with language-specific blocks in the description? .. right, I didn't think so. Feel free to add a suggestion, go to GitHub or Discord to make your case.
I don't like that there's a column named
id
and no mention of it. It disables the solution starting withSELECT love.*,
.As a general remark, adding SQL-specific requirements as a comment in the solution template is a practice with poor usability. I suggest Codewars let translations (as well as original kata statements) consist of the universal part and a language-specific one.
love is now on dart
Translation Dart
smart guy
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
Well it should be best practice cause mine is the real clever one
Great kata, good practice with logical operators!
Go to Solutions, scroll down, see if you find such solution.
This comment is hidden because it contains spoiler information about the solution
Loading more items...