So here's the rules that this kata's should have :-

1. The solution should use SELECT, WHERE, ORDER BY query
2. The solution should have 3 columns namely id, name, stock

please note that we need only those rows that have stock 2 or less than two and that FROM companyA

so the rule for this kata is that your solution should have :-

1. SELECT query
2. WHERE query
3. LIKE query not use LEN query [dont know why]
4. contain 2 columns namely first_name and last_name
5. should return rows that have MORE THAN 6 characters

that's it

Your math made me smile :)

If your test fails, check two things:

1. What data type ROUND() accepts as its first argument in PostgreSQL
2. What output data type the kata expects

Actually, it seems like it doesn't matter what order the columns are in the output. Looking at the tests, they should really just be rewritten from scratch

The output schema in instructions is wrong you need to have

name, price, price_per_kg, weight

main difference is weight is last not second.

Very good kata all in all.

DATABASE name would be nice.
.
.
.
Its "products"
nevermind, im too stupid to read :)

I think ROUND needs a numeric type, not double precision

Satisfying Kata, thank you

Nice kata! A simple formula at its core, but a great opportunity to think recursively and iterate mentally. Clean, well-structured challenge. Thanks for creating this!

Your calculation of price_per_kg is wrong. Look at the table that your query generates. When I run your query, it tells me that for something that costs 2.44 and weighs 30 grams, the price_per_kg is 0.07. That doesn't make any sense, does it? If it costs 2.44 for less than 1kg, how would a kg cost 0.07? If you fix your calculation, I think you'll find that the kata is not bad and is not a waste of time.

I can't for the life of me figure how how my solution is different from the "correct" one. Even after fighting Postgres... this Kata is bad. Don't waste your time.

Hated it.

This is one of those exercises that’s more about fighting PostgreSQL's quirks than about actually understanding SQL concepts.