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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,236576d8947fc908,start
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news2.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail
Newsgroups: comp.lang.ada
Subject: users of GNADE MySQL binding?
From: Stephen Leake <stephen_leake@stephe-leake.org>
Date: Tue, 08 Sep 2009 07:18:36 -0400
Message-ID: <u63btadmb.fsf@stephe-leake.org>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (windows-nt)
Cancel-Lock: sha1:6zjHshISrfeIiy+5pTMY60OfgKs=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@flashnewsgroups.com
Organization: FlashNewsgroups.com
X-Trace: 80c914aa63d30e197caa731559
Xref: g2news2.google.com comp.lang.ada:8228
Date: 2009-09-08T07:18:36-04:00
List-Id: <comp.lang.ada>

I'm considering becomming the Debian maintainer of GNADE.

In going over the code while preparing a release, I realized that the
C structs that had been duplicated in Ada records in the GNADE MySQL
binding are now wrong; they have changed significantly with each MySQL
release, and GNADE has not kept up.

Therefore the MySQL binding in GNADE 1.5.3 (currently in Debian Lenny)
most likely doesn't work, so I'm thinking no one uses it.

Rather than fixing it now, I'm considering dropping that library from
the Debian release. I'll still package the ODBC binding, which does
work with MySQL.

Any objections? Comments?

I still need to review the other GNADE bindings, to Sqlite3 and
Postgre, for similar issues.

Previous versions of the GNADE Debian package included the Sqlite
binding; this will be the first to include Sqlite3 instead. Does
anyone still use Sqlite (not Sqlite3)? It would not be very hard to
include both, aside from the effort required to review the C bindings.

-- 
-- Stephe