SEO

#1 (**permalink**) 04-16-2008, 01:48 AM

> -----Original Message-----
> From: Ludek Finstrle [mailto:luf@pzkagis.cz]
> Sent: 26 January 2006 10:18
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Odbcapi30.c - 64 bit compiler warning cleanup
>
> > The attached patch cleans up the 64 bit compiler warnings in
> > odbcapi30.c.
>
> I test it and add more warning cleanups. I include your patch into
> attached one. I tried it a little bit on 64-bit and 32-bit box.

Compiles without errors or warnings here.

> I don't solve the problem in options.c where 64-bit pointer may
> be passwd throught 32-bit number. I don't know how to solve it.

No nor I. Any chance of a little help with this one please Tom?

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#2 (**permalink**) 04-16-2008, 01:48 AM

"Dave Page" <dpage@vale-housing.co.uk> writes:
>> From: Ludek Finstrle [mailto:luf@pzkagis.cz]
>> I don't solve the problem in options.c where 64-bit pointer may
>> be passwd throught 32-bit number. I don't know how to solve it.

> No nor I. Any chance of a little help with this one please Tom?

I assume that you can't alter the signature of PGAPI_SetConnectOption,
ie, vParam really has to be SQLUINTEGER and not some other type?

If so, I'd argue that that whole block (the "if (fOption == 30002 &&
vParam)" stuff) ought to be #ifdef WIN32. It's certainly useless on
any other platform, and Microsoft is never going to figure out how
to 64-bit-ify that pile of junk they call an OS, so no need to bend
our brains wondering how this would work on 64-bit Windows.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Odbcapi30.c - 64 bit compiler warning cleanup