Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rjbqd-006eWx-Lc for pgsql-odbc@arkaria.postgresql.org; Mon, 11 Mar 2024 09:21:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rjbqc-00B62c-9P for pgsql-odbc@arkaria.postgresql.org; Mon, 11 Mar 2024 09:21:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rjbqc-00B62T-2f for pgsql-odbc@lists.postgresql.org; Mon, 11 Mar 2024 09:21:30 +0000 Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rjbqZ-003vVA-1q for pgsql-odbc@postgresql.org; Mon, 11 Mar 2024 09:21:29 +0000 Received: by mail-yb1-xb2c.google.com with SMTP id 3f1490d57ef6-dc25e12cc63so4737631276.0 for ; Mon, 11 Mar 2024 02:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710148887; x=1710753687; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=QB5IaLBb6K5aKZGhP7ePR+Smb1tZRbg9ojcGCyVPfwU=; b=iXKGHN4r7nk0VBKBTyT5tb9ZYxVhCdJvGQpcVHRJSt76FDQ8TDeIkfF1Z0LmfmjyID scCMKqmCjLuXd/LL+m7pRWSnI9Y5/hbpzyO9nUcuWkOvus4Sii+ZOTQsEftSLMbzfT/K 1KyUjeU+N5pcx95mj4GQG+rjbD6q4yyR1Aa7iNeuxbBUsOz78XwXnzORKKvahcunh8JC mIii8yykZdNL6ozqpcsLYnrOXD3d8NzNbLinUfIuhsKMGpWEDu6x7SRX/27p91v2zFVb X8/phsSBsV6KtVr/FPLKAHzmXEEwfWvubpzFM2NjksdWsUigBFynLYUzT1nmCYri5jWk pc8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710148887; x=1710753687; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=QB5IaLBb6K5aKZGhP7ePR+Smb1tZRbg9ojcGCyVPfwU=; b=adPH3LEtkybcrX0iwm67rIM7xEnQNHW3j6K26fjGlqgU7qqdEnjwaBzrDyGcJF493K j/wT+GgOMAvJv7jE5cWdeAfFFtcfc9T5622DdfiaaFS3sAVg/A5+uZZVQgU+CCXkRrDd tRyXU4RELAOfgBy9fdi7C26ZZTkn/GwKF4ECOjZArNGjec9Dcxohr+y/Z+gUwtKsmEVA WyljXHqlkKyW9XG3xwmPJpKGJ2olkNTU363+N3ugv7d78AMJtRVnjHYkE975FDXptj6R BJryT6DRz6AU+wBL6NFCkLIKpXJHv/9SwEK+iy2WLRQXS82ebi5laGqYG5X0yQzH02Ev HCbA== X-Gm-Message-State: AOJu0YygWMEKeo8xPhG7QmJYuvem3yzPLbX42qMGfy9UR9Jy0JJRDrAo y+si3HHoDQBI9nkc4uT7xv5fMC8lnUggAFvRRxf32QisiBP/bIpzpFTWgSViN44MP5gvNQvpZLH cb4iSZpnHry3DNGW0fjtz2RN8Ty8FzyNHFNI= X-Google-Smtp-Source: AGHT+IGGv7bhPpX/s5ldVaugc7Rr+2Gy0HmY/QC7+7gq8uMEYQSfM/4U6bnXGuuEOuaOaDLNmK0OQXnLj3dEIKzTtiU= X-Received: by 2002:a25:d015:0:b0:dc6:ab85:ba89 with SMTP id h21-20020a25d015000000b00dc6ab85ba89mr3836502ybg.25.1710148886570; Mon, 11 Mar 2024 02:21:26 -0700 (PDT) MIME-Version: 1.0 From: Karl Aschbacher Date: Mon, 11 Mar 2024 10:21:15 +0100 Message-ID: Subject: Value changed from Integer to Double To: pgsql-odbc@postgresql.org Content-Type: multipart/alternative; boundary="000000000000e5aefc06135f1051" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e5aefc06135f1051 Content-Type: text/plain; charset="UTF-8" Dear all, we are facing a problem that is maybe related to the postgres-odbc driver. We use Oracle Analytics Server via ODBC to talk to a postgres Database (V15) It appears that integers with more than 10 digits get converted to doubles when the statment is being sent to the database. So for example: "where id = 32857641330" will be converted to "where did = 3285764133.0 " So my question is - does the driver play any role when preparing the statement? (Like providing the PG Type ?) In case it does, would anyone have a suggestion where to look for the potential issue? many thanks best regards Karl --000000000000e5aefc06135f1051 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

we are facing a problem that = is maybe related to the postgres-odbc driver.
We use Oracle Analy= tics Server via ODBC to talk to a postgres Database (V15)
It appe= ars that integers with more than 10 digits get converted to doubles when th= e statment is being sent to the database.
So for example: "w= here id =3D=C2=A0 32857641330" will be converted to "where did = =3D 3285764133.0 "

So my question is - does t= he driver play any role when preparing the statement?
(Like provi= ding the PG Type ?)
In case it does, would anyone have a suggesti= on where to look for the potential issue?

many tha= nks
best regards
Karl
--000000000000e5aefc06135f1051--