> Actually, I'm rather surprised to see 'real' there: if you're using setObject with a Long, I would imagine that turns
> into a bigint (which I believe the server knows how to coerce to numeric).
The (real) is just my fault in testing. I just copy/pasted from elsewhere and it is not what is coming from the JDBC
driver, I don't know how to see what the driver is actually sending.