Re: int8 becames string in BDE :-(

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: SZUCS Gábor <surrano(at)mailbox(dot)hu>
Cc: <pgsql-odbc(at)postgresql(dot)org>, "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
Subject: Re: int8 becames string in BDE :-(
Date: 2002-06-05 07:48:46
Message-ID: D85C66DA59BA044EB96AB9683819CF610150C1@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Ahh, I see. In that case I would not be opposed to such a change. However, as Hiroshi points out in his reply, mapping int8 -> int4 may cause problems when you do get numbers bigger than 2,147,483,647 but of course, that may not apply to your situation.

Regards, Dave.

> -----Original Message-----
> From: SZUCS Gábor [mailto:surrano(at)mailbox(dot)hu]
> Sent: 04 June 2002 17:31
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] int8 becames string in BDE :-(
>
>
> Dear Dave,
>
> Oh no and oh yes, you are both right and wrong. Let me explain.
>
> ----- Original Message -----
> From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
> Sent: Tuesday, June 04, 2002 6:00 PM
>
>
> > Is it possible, and, if not a significant work, would you
> > (Hiroshi) add another choice, namely, int4? (argh :) ) It
> would be a
> > real quick fix to our problem to help change between the databases.
> <<<
> What's wrong with int4? I don't recall hearing of any
> problems with them
> >>>
>
> No problem with int4. Now I see that I wasn't crystal clear
> about my question. I asked if it's possible to add the driver
> another option to convert int8 to int4 (SQL_INTEGER or whatsis).
>
> <<<
> in the last 5 years or so. If this request is to make your
> life easier on your current project rather than fix an actual
> bug, then I would
> >>>
>
> Yes, it's to make our lives easier. It would be a necessary
> adjustment for us to change from PostgreSQL 7.1.3 to 7.2, or
> else the workaround would be a real pain (revisit all
> queries, server-side functions, triggers and tables). This
> could be done in time but it is time we really don't have
> much to change to 7.2. I.e, once we have 7.2 working, we'll
> have time to do the workaround and drop this excuse of an option.
>
> This is why I tried to ask Hiroshi as humbly as my English
> allows to see if it's easily done.
>
> As for the source, I'm unsure if we have the development
> tools to compile the driver, but if nobody else will do it --
> well, we'll have to do it ;)
>
> <<<
> The code in question is in pgtypes.c - the int8 hacks have the comment
> /* Change this to SQL_BIGINT for ODBC v3 bjm 2001-01-23 */
> above them for reference.
> >>>
>
> Thanks for the reference, It's really valuable.
>
> Yours,
> Gábor
> --
> There are 10 kinds of people:
> those who understand binary numbers and those who don't.
>
>

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message SZUCS Gábor 2002-06-05 08:12:58 Re: int8 becames string in BDE :-(
Previous Message Hiroshi Inoue 2002-06-05 06:40:58 Re: int8 becames string in BDE :-(