I'm not sure what your question is.

Amines are tricky, because they can be named in two different ways. Either "ramifications+amine", or "main-chain+ramifications+amine".

So, you have from 1 to 3 carboned chains on the N, and either all of them are named as ramifications, or one can be named as a "main chain". Here, the dimethyl part is after what looks like the main chain (ethan) so they aren't on that chain but on the N. The 1 refers to the position of the N on the main chain (since we are in "way 2" aka [ramifications on main chain]main-chain-(pos-suffix) and here, the suffix is [dimethyl]amine, kinda).

So you end up with what's on the left of that name in the description:

suffix-CH2-CH3  as ethan-1-suffix

H3C-N-CH2-CH3   with suffix = [dimethyl]amine
    |
    CH3

Oh, duh! You actually found a bug: the list of prefixes isn't up to date and still contains anoyloxy instead of oyloxy...
I'll update that, thx. (edit: done)

The name is valid.

8-([but] [-3-yn] [oyloxy]) oct [-3,5,7-triyn] oic acid
   .....         ......... ^^^                ^^^^^^^^

Is that enough?

.

The message and the description need to be fixed, yes. Just leave this issue open and someone will take care of this.

I just checked the code of tests to make you able to m9ve forward before the problem gets addressed.

I will try to improve the message, but you'd have to tell me the language you are attempting.

EDIT: your solution most probably triggers this condition of the anti-cheat: sol.includes('Function').

Thanks, I have lots of inspiration atm, so I'm taking advantage of that to author kata's. Btw, you are free to ignore any tables or fields you don't need.

• 24  PERFORM create_temp_tables(product_identifier);
  25  WITH
  

  ⬇

  24  PERFORM create_temp_tables(product_identifier); WITH
  

• 60  cur_date = end_dates[i];
  61  SELECT
  

  ⬇

  60  cur_date = end_dates[i]; SELECT
  

Long story short, it's a problem with the ruby test library from codewars (the run_sql function incorrectly truncates the literal string in some cases).

I can take a look at it if you post your code. :)

no pain, no gain

You could use a select statement to iterate all tables and build insert statements from that using dynamic sql. I can't think of an easier way.

msg is like a print.

When you write in a code print("a\nb") you don't expect to get \n visible in the console, you expect the b on the next line. Hence print is interpreting the double char you wrote as the escaped chr(10) (iirc, it's 10... didn't check). So must do msg.

Now, the problem is that you're writting a code that sort of interprets that print statement. And there, you want the line feed to be "humanly readable" in the generated code, hence, that code is outputting \\n, so that the final compiled code actually contains \n.

Not sure this is clear... Probably not... Cannot do better, sorry. To summarize, it's about the difference between what you actually type, and what's printed from that.

I was between 3 and 4 kyu, but I'd say 4 is reasonable.

I was inspired by a 3 kyu kata on binomial expansion which was admitedly easier than this one. However, that one was severely overated.

So yeah, I'm happy with 4 kyu. I't nice to have this kata finally approved after 5 months.