I have used the next SQL statement in both MySQL and PostgreSQL:
db.Query(`SELECT COUNT(*) as N FROM email WHERE address = ?`, email)
But it fails in PostgreSQL with this error:
pq: F:"scan.l" M:"syntax error at end of input" S:"ERROR" C:"42601" P:"50" R:"scanner_yyerror" L:"993"
What's the problem? The error messages in PostgreSQL are very cryptic.
You haven't provided any details about the language/environment, but I'll try a wild guess anyway:
MySQL's prepared statements natively use ? as the parameter placeholder, but PostgreSQL uses $1, $2 etc. Try replacing the ? with $1 and see if it works:
WHERE address = $1
The error messages in PostgreSQL are very cryptic.
In general, I've found that Postgres error messages are better than competing products (ahem, MySQL and especially Oracle), but in this instance you've managed to confuse the parser beyond sanity. :)
?. The idea of having different placeholders based on DB driver is pretty horrid.
?) forces the client side to implement full SQL parser matching that of the target DB engine. Moreover, $N potentially allows you to specify one value for several placeholders while ? does not.
? is easy. But it's a hell of a lot harder if you consider that ? is a valid character within strings -- and shouldn't be changed there! Coupled with all the possible different escaping rules, which depend on server-side settings and Postgres versions, along with some pretty complicated parsing cases involving PostgreSQL's $foo$?$foo$ syntax. It gets VERY nasty.In golang for queries we have use
You are using Go right?
try:
db.Query(`SELECT COUNT(*) as N FROM email WHERE address = $1`, email)
In my case, it was due to using a -- line comment where the program that was responsible for interacting with the database read in the multiple lines of my query all as one giant line. This meant that the line comment corrupted the remainder of the query. The fix was to use a /* block comment */ instead.
Another possibility - check for any missing END directives for IF, LOOP, etc.
I'd been working in a loop so long, that I didn't realize I never put in an END LOOP;.
The message that Postgres displays:
ERROR: syntax error at end of input
LINE 123: $$;
is terribly unhelpful at telling you if some construct was never closed.
One cause for this error can be that you are missing a terminating semi-colon before your final END statement, for example
return True
END;
$$
LANGUAGE plpgsql;
which should be
return True;
END;
$$
LANGUAGE plpgsql;
psql.PREPARE q AS SELECT COUNT(*) as N FROM email WHERE address = $1;thenEXECUTE q;.$1is the placeholder syntax forPREPARE, but your programming language probably uses?; otherwise there's no difference.