Why did we get this error, though? Well, behind the scenes, there might be a SQL statement

Psst: INPUT will be replaced with your actual input.