I guess it would have to be changed because if there is some other column that gets added to the table, then we would have to update the query and select the newly added column as well.
If we use select ALL(select * ) we won't have to edit the query, as it selects all the columns there are to select.
many (charP ' ') will accept any amount of spaces. some (charP ' ') will not accept the empty string. They are in some way similar to even and odd. Your implementation may fail at some of the other parsers.
@AndrewSouthpaw
I guess it would have to be changed because if there is some other column that gets added to the table, then we would have to update the query and select the newly added column as well.
If we use select ALL(select * ) we won't have to edit the query, as it selects all the columns there are to select.
many (charP ' ')will accept any amount of spaces.some (charP ' ')will not accept the empty string. They are in some way similar toevenandodd. Your implementation may fail at some of the other parsers.Can you explain your reasoning there? Why should the query have to be edited if the table's column set changes?
This comment is hidden because it contains spoiler information about the solution
Hey, thanks!
Yes, indeed, we shouldn't modify the input. I should have thought of that!
Yeah :) Tests should be updated.
This was already a posted issue, do not re-post it, please.