From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,8d52d4fbf051d828
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.180.106.199 with SMTP id gw7mr3228610wib.0.1347408928124;
        Tue, 11 Sep 2012 17:15:28 -0700 (PDT)
Path: 
 ed8ni19587634wib.0!nntp.google.com!feeder1.cambriumusenet.nl!194.109.133.85.MISMATCH!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!feeder3.cambriumusenet.nl!feed.tweaknews.nl!216.40.29.245.MISMATCH!novia!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsgate.cuhk.edu.hk!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: Status of GNADE ODBC under Debian 64-bit
Date: Tue, 4 Sep 2012 13:54:14 +0200
Organization: cbb software GmbH
Message-ID: <1bujq0y5qhbut$.omax4w4vmm7$.dlg@40tude.net>
References: <fw8uijju18zy$.11cg80j2ky77j$.dlg@40tude.net>
 <474c2d57-9ac8-42f0-afd1-b32e4d8118b5@googlegroups.com>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: 2012-09-04T13:54:14+02:00
List-Id: <comp.lang.ada>

On Tue, 4 Sep 2012 02:40:32 -0700 (PDT), Graham Stark wrote:

> I'm interested in this as I use GNADE quite a bit. 
> 
> If you just change SQLUINTEGER to SQLUBIGINT in the indicated places Ludovic's
> warning goes away.

Maybe, but he reported rather a need to verify consistency on 64-bit
platform.

Should I report it independently to sourceforge?

> The SQLLEN thing looks like a different problem and really quite nasty - I
> hadn't come across this before. My reading of it is that some ODBC drivers
> might need 32 bits there even on 64 bit systems; see this, for instance:
> http://www.martin-evans.me.uk/node/99
> 
> I have notice some funny behaviour retrieving strings from databases,
> where the length is not returned correctly, so maybe that's the cause.
> Never seen a crash, though.

Specifically to unixodbc and Debian, the macro BUILD_LEGACY_64_BIT_MODE if
defined in sqltypes.h, makes SQLLEN 32-bit. When undefined it is 64-bit.
The effect of SQLINTEGER (always 32-bit) passed instead of 64-bit is memory
corruption.

It should also become an issue for native Windows 64-bit applications, once
GNAT to support them.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de