Re: After upgrading libpq, the same function(PQftype) call returns a different OID

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: After upgrading libpq, the same function(PQftype) call returns a different OID
Date: 2025-03-20 15:33:07
Message-ID: f14fee4e-82ce-4cfe-9f0d-19292a372968@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/20/25 00:17, Sebastien Flaesch wrote:
> Let's not deviate from my request:
>
> I have implemented various DB client modules using the C client APIs,
> for Oracle DB, SQL Server, IBM DB2, MySQL/MariaDB, SQLite and PostgreSQL.
>
> While I like PostgreSQL a lot, this is the only case where I have to
> define myself the column type ids, to implement a "describe column" feature.
>
> ODBC has SQLDescribeCol() / SQLDescribeColW() and predefined SQL_*
> constants like SQL_INTEGER, SQL_VARCHAR ...
>
> Native PostgreSQL built-in SQL types should be listed in a .h header of
> the C client API
>

You could borrow from here:

https://github.com/postgresql-interfaces/psqlodbc/blob/main/pgtypes.h

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-03-20 15:38:27 Re: Bloated toast table with empty associated table
Previous Message Nathan Bossart 2025-03-20 15:18:16 Re: Disabling vacuum truncate for autovacuum