title: How to reproduce with a manual query: [Amazon](500310) Invalid operation: failed to find conversion function from "unknown" to integer;
body: <p>I recently added a maven dependency to a Dropwizard project:</p>
  <pre><code>        &lt;dependency&gt;
              &lt;groupId&gt;com.amazon.redshift&lt;/groupId&gt;
              &lt;artifactId&gt;redshift-jdbc42-no-awssdk&lt;/artifactId&gt;
              &lt;version&gt;1.2.45.1069&lt;/version&gt;
          &lt;/dependency&gt;
  </code></pre>
  <p>which is replacing the <code>org.postgresql.Driver</code> previously used, and since then some of my queries are returning</p>
  <pre><code>! Causing: org.skife.jdbi.v2.exceptions.UnableToCreateStatementException: java.sql.SQLException: [Amazon](500310) Invalid operation: failed to find conversion function from &quot;unknown&quot; to integer;
  </code></pre>
  <p>I suspect I might have dozens of queries that will need adapting to work with the new driver.</p>
  <p>Because I don't want to have to restart my server every time I want to test whether a change to a query fixes the problem, I want to run the queries manually against the Redshift DB, so that I can quickly identify the part of the query that needs fixing.</p>
  <p>My problem: I cannot reproduce the error when running the query manually from inside an IntelliJ DB Console. I even downloaded the JAR of the Amazon Redshift Driver from <a href="https://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html</a> (I downloaded this one: <a href="https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/1.2.45.1069/RedshiftJDBC42-no-awssdk-1.2.45.1069.jar" rel="nofollow noreferrer">https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/1.2.45.1069/RedshiftJDBC42-no-awssdk-1.2.45.1069.jar</a>) and used it to set up a new DB connection in IntelliJ. But still, running the exact same query manually from the IntelliJ DB Console won't give me the error.</p>
  <p>Can anyone think of what configuration might be causing the query to give an error when run by the server compared to running it manually from the Console ? And how to get it to either stop throwing the exception on the server or start causing the same error when run in a Console ?</p>