From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Abhishek Kumar <abhishek(dot)aak0(at)gmail(dot)com> |
Cc: | pgsql-odbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: DataType bytea Precision returning a negative value |
Date: | 2024-07-11 12:54:31 |
Message-ID: | CADK3HHKM-LMdHVC6dZFoRjsLo3CpXv3V-d_a_pr++BWQhVvvwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Thu, 11 Jul 2024 at 04:56, Abhishek Kumar <abhishek(dot)aak0(at)gmail(dot)com>
wrote:
> Hi,
>
> When we query the psqlodbc driver to get the column information of the
> table(via SQLColumns), we get a precision value of -4 for bytea column. Is
> this expected to happen? If yes, what does this value mean for a bytea
> column. If no, then what is the correct expected behavior?
>
Looks like we return
switch (handle_unknown_size_as)
{
case UNKNOWNS_AS_DONTKNOW:
return SQL_NO_TOTAL;
}
Because we don't know the length.
Dave
>
From | Date | Subject | |
---|---|---|---|
Next Message | Chang Lu | 2024-07-18 09:54:14 | [bug-report]SQLRowCount set affected row numbers is incorrect when use SQLBindParameter and SQLSetStmtAttr for SQL_ATTR_PARAMSET_SIZE |
Previous Message | Dave Cramer | 2024-07-11 12:46:42 | Re: Query regarding Bind data type, precision, scale while using psqlodbc |