Message-ID: <gh-postgresql-interfaces-psqlodbc-82-c2555005662@github.com>
From: "JacoboSanchez (@JacoboSanchez)" <noreply+JacoboSanchez@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Thu, 19 Dec 2024 16:40:49 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #82: Is this expected a bind to BIGINT to be surrounded by quotes?
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-82@github.com>
References: <gh-postgresql-interfaces-psqlodbc-82@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: JacoboSanchez
X-GitHub-Comment-Id: 2555005662
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 82
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/82#issuecomment-2555005662
Content-Type: text/plain; charset=utf-8

Well it is a bit more complicated

Think on it as a middleware receiving the query from ODBC and generating a delegation to JDBC.

- client prepares a `select * from view where field = ?` and binds it to bigint 333
- Driver translates it to `select * from view where field = '333'` (this works on PostgreSQL so there is no bug there)
- I get that query and translate it to PostgreSQL JDBC prepared statement `select * from view where field = ?` and bind it in the JDBC way by using a `setString`
- This fails 

This is more or less how ended up asking for the reason to format the bigint binding with quotes in ODBC :)