• Sign Up
    Time to claim your honor
  • Training
  • Practice
    Complete challenging Kata to earn honor and ranks. Re-train to hone technique
  • Freestyle Sparring
    Take turns remixing and refactoring others code through Kumite
  • Community
  • Leaderboards
    Achieve honor and move up the global leaderboards
  • Chat
    Join our Discord server and chat with your fellow code warriors
  • Discussions
    View our Github Discussions board to discuss general Codewars topics
  • About
  • Docs
    Learn about all of the different aspects of Codewars
  • Blog
    Read the latest news from Codewars and the community
  • Log In
  • Sign Up
ArtificialCyst Avatar
Name:Unknown
Clan:Unknown
Member Since:Oct 2019
Last Seen:Dec 2021
Profiles:
    Following:0
    Followers:0
    Allies:0
    View Profile Badges
    • Stats
    • Kata
    • Collections
    • Kumite
    • Social
    • Discourse
    • Conversations (9)
    • Replies
    • Authored
    • Needs Resolution
    • Custom User Avatar
      • uniapi
      • resolved an issue on "GROCERY STORE: Logistic Optimisation" kata
      • 6 years ago

      The answer is below...

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Basics: Simple VIEW" kata
      • 6 years ago

      I would say it's better to do the actual task and create a view instead of trying to get around the proper task. It's stupid to exercise and not do it properly.

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Basics: Simple VIEW" kata
      • 6 years ago

      You need order the results ascending and then it works because the expected results are ordered as well. It shouldn't be like this cuz there is nothing about ordering the results in the instructions

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Basics: Simple VIEW" kata
      • 6 years ago

      Oh snap, I read it totally differently, now I see the point.

    • Custom User Avatar
      • ArtificialCyst
      • created an issue for "GROCERY STORE: Logistic Optimisation" kata
      • 6 years ago

      This comment is hidden because it contains spoiler information about the solution

    • Custom User Avatar
      • matt c
      • commented on "SQL Bug Fixing: Fix the JOIN" kata
      • 6 years ago

      In version 2, don't forget to wrap the whole field when converting to a float..

      e.g. (trunc(SUM(J.salary)*100)/100)::float

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Bug Fixing: Fix the JOIN" kata
      • 6 years ago

      Deleted the semicolon and it works. Semicolons are really a powerful weapons in CodeWars. :P

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Bug Fixing: Fix the JOIN" kata
      • 6 years ago

      Every value rounded to 2 decimals and still not passing the test. What's going on? :(

    • Custom User Avatar
      • ArtificialCyst
      • commented on "SQL Bug Fixing: Fix the JOIN" kata
      • 6 years ago

      Same here, every value rounded to 2 decimals and still not passing the round test. :/

    • © 2025 Codewars
    • About
    • API
    • Blog
    • Privacy
    • Terms
    • Code of Conduct
    • Contact

    Confirm

    • Cancel
    • Confirm

    Collect: undefined

    Loading collection data...