Helpful comment, thank you.
For ones who has PG::NumericValueOutOfRange: ERROR: integer out of range check 220.127.116.11. Constants of Other Types or this Stack Overflow answer. Documentation about recursive request creation could be found here 7.8.1. SELECT in WITH.
PG::NumericValueOutOfRange: ERROR: integer out of range
This kata has poor description but brings profit.
Thanks @eliseuvideira for the comment.
And thanks the kata author for his work too.
Why the heck there's a test with 10_000_000 and there's no mention of that anywhere?
It was really hard to figure out what to do because:
This is kind of mess in description that makes people go wrong way many times during solving the kata. Please make instructions clear for SQL
Not a kata issue, but a codewars issue, works fine with my code tho.
"already approved some time ago"
This comment is hidden because it contains spoiler information about the solution :P
In the php tests the values of the test methodes should be the reverse. When a answer is wrong your answers shows up as expected instead of actual.
How it is now:
$this->assertEquals(crossover('00000000', '11111111', 7), ['00000001', '11111110']);
How it sould be:
$this->assertEquals(['00000001', '11111110'],crossover('00000000', '11111111', 7));
Test.expect(crossover('111000','000110',3) === '111110' && crossover('111000','000110',3) === '000000');
Should the second one expect '000010'?
Caught unexpected signal: 6
I dont know why im getting this in C
Seems already fixed