From bas.driessen@xobas.com Sat Aug 1 07:19:12 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id C666A750122 for ; Sat, 1 Aug 2009 07:19:12 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 11821 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wun9rDeDLBN1 for ; Sat, 1 Aug 2009 07:19:06 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 5579D7500FF for ; Sat, 1 Aug 2009 07:18:58 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n717Ik0T015076 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 1 Aug 2009 17:18:53 +1000 From: Bas Driessen To: Vivien Malerba In-Reply-To: References: <1248938750.8918.34.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-WJSOb29kFh5LyBGmEB8h" Organization: Xobas Software Date: Sat, 01 Aug 2009 17:18:40 +1000 Message-Id: <1249111120.3242.2.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9641/Sat Aug 1 13:14:07 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] mysql create index patch. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Aug 2009 07:19:13 -0000 --=-WJSOb29kFh5LyBGmEB8h Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 2009-07-30 at 10:13 +0200, Vivien Malerba wrote: > > > > 2009/7/30 Bas Driessen > > Hello, > > Please find attached a mysql create index patch. This will > allows for the quoting of field names in the index itself. > Patch generated with libgda git master 29/07/2009. > > Please review and apply to master if OK. > > > Ok, will apply it ASAP. I just applied this myself as a first test on both Master as LIBGDA4_0 branch (as it was a bugfix). Please review if all looks good. Thanks, Bas. --=-WJSOb29kFh5LyBGmEB8h Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Thu, 2009-07-30 at 10:13 +0200, Vivien Malerba wrote:


2009/7/30 Bas Driessen <bas.driessen@xobas.com>
Hello,

Please find attached a mysql create index patch. This will allows for the quoting of field names in the index itself. Patch generated with libgda git master 29/07/2009.

Please review and apply to master if OK.


Ok, will apply it ASAP.

I just applied this myself as a first test on both Master as LIBGDA4_0 branch (as it was a bugfix). Please review if all looks good.

Thanks,
Bas.

--=-WJSOb29kFh5LyBGmEB8h-- From bas.driessen@xobas.com Mon Aug 3 11:19:41 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 472667500D0 for ; Mon, 3 Aug 2009 11:19:41 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 21 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dS0yEpMVExOx for ; Mon, 3 Aug 2009 11:19:34 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 60501750066 for ; Mon, 3 Aug 2009 11:19:25 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n73BJHO8006506 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 3 Aug 2009 21:19:20 +1000 From: Bas Driessen To: Vivien Malerba In-Reply-To: References: <1248956551.4329.4.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-In3mJwLGTxzk0BR3lIhH" Organization: Xobas Software Date: Mon, 03 Aug 2009 21:19:16 +1000 Message-Id: <1249298356.31893.32.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9646/Mon Aug 3 19:55:22 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] Meta Store issue with MySQL. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 11:19:41 -0000 --=-In3mJwLGTxzk0BR3lIhH Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote: > > > > 2009/7/30 Bas Driessen > > > > 2009/7/30 Bas Driessen > > > >> Hello, > >> > >> My database is in MySQL. When I run the following command > to rebuild the > >> MetaStore (which lives in a sqlite3 database): > >> > >> gda_connection_update_meta_store(connection, NULL, &error) > >> > >> I get the following error/warning: > >> > >> ** (process:22406): WARNING **: (+5): Wrong Holder value > type, expected > >> type 'boolean' when value's type is 'string' (Provider > ThreadWrapper) > >> > >> > >> and the MySQL table information is not in the MetaStore. In > fact if I > >> do: > >> > >> select * from _tables; > >> > >> nothing shows up. > >> > >> Anyone else having this problem? > >> > > > > The reason for this error is that a SELECT statement > internally run by the > > MySQL provider to get meta data returned a column of type > string instead > > to > > a boolean. To solve this, the correction consists in > locating the faulty > > SELECT, and use > gda_connection_statement_execute_select_full() with an > > array > > of expected types for the columns instead of > > gda_connection_statement_execute_select(). This is already > done at several > > places in gda-mysql-meta.c. > > > > If you want to try to correct it, and if you are in the > master branch, you > > can use the definitions in > > libgda/providers-support/gda-meta-column-types.h > > (which is dynamically generated). > > > > Otherwise, I'd need to have more information to correct the > problem > > myself. > > > > OK, I will try to locate and correct the issue in libgda. Just > wanted to > have confirmed first that this is an issue in libgda and not > in my setup. > > > To help you, you can uncomment the line 2324 of the gda-meta-store.c > file, so you'll get debug info about all the results the provider is > returning for the meta store. OK, I am a step further in this (I think). In file providers/mysql/gda-mysql-meta.c, line 717 the structure should be changed from: GType col_types_views[] = { G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE }; to: GType col_types_views[] = { G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE }; The original error will be gone and it will continue past the point where it stopped. However, there are now many new error messages: (process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Type gchararray not mapped for value 0 (process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Type gint not mapped for value (null) (process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Invalid column bind data type. 253 (this repeats many many times) ============ (process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Unable to get value for row 0 and column 10 ** (process:8055): WARNING **: Type gint not mapped for value (null) (Provider ThreadWrapper) As a rollback is triggered, the meta store is empty. I have no idea if I am pretty close to have this all working, or if this whole area is still up for a re-write/under development. See also my previous thread for a reproducible case of this issue. Any comments/tips/hints? Thanks, Bas. --=-In3mJwLGTxzk0BR3lIhH Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote:


2009/7/30 Bas Driessen <bas.driessen@xobas.com>

> 2009/7/30 Bas Driessen <bas.driessen@xobas.com>
>
>>  Hello,
>>
>> My database is in MySQL. When I run the following command to rebuild the
>> MetaStore (which lives in a sqlite3 database):
>>
>> gda_connection_update_meta_store(connection, NULL, &error)
>>
>> I get the following error/warning:
>>
>> ** (process:22406): WARNING **: (+5): Wrong Holder value type, expected
>> type 'boolean' when value's type is 'string' (Provider ThreadWrapper)
>>
>>
>> and the MySQL table information is not in the MetaStore. In fact if I
>> do:
>>
>> select * from _tables;
>>
>> nothing shows up.
>>
>> Anyone else having this problem?
>>
>
> The reason for this error is that a SELECT statement internally run by the
> MySQL provider to get meta data returned a column of type string instead
> to
> a boolean. To solve this, the correction consists in locating the faulty
> SELECT, and use gda_connection_statement_execute_select_full() with an
> array
> of expected types for the columns instead of
> gda_connection_statement_execute_select(). This is already done at several
> places in gda-mysql-meta.c.
>
> If you want to try to correct it, and if you are in the master branch, you
> can use the definitions in
> libgda/providers-support/gda-meta-column-types.h
> (which is dynamically generated).
>
> Otherwise, I'd need to have more information to correct the problem
> myself.


OK, I will try to locate and correct the issue in libgda. Just wanted to
have confirmed first that this is an issue in libgda and not in my setup.

To help you, you can uncomment the line 2324 of the gda-meta-store.c file, so you'll get debug info about all the results the provider is returning for the meta store.

OK, I am a step further in this (I think). In file providers/mysql/gda-mysql-meta.c, line 717 the structure should be changed from:

GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE
        };

to:


GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE
        };

The original error will be gone and it will continue past the point where it stopped. However, there are now many new error messages:


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gchararray not mapped for value 0

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gint not mapped for value (null)

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Invalid column bind data type. 253

(this repeats many many times)
============


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Unable to get value for row 0 and column 10

** (process:8055): WARNING **: Type gint not mapped for value (null) (Provider ThreadWrapper)

As a rollback is triggered, the meta store is empty.

I have no idea if I am pretty close to have this all working, or if this whole area is still up for a re-write/under development.

See also my previous thread for a reproducible case of this issue.

Any comments/tips/hints?

Thanks,
Bas.



--=-In3mJwLGTxzk0BR3lIhH-- From jhs@jsschmid.de Mon Aug 3 20:18:48 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 10B8C7500DC for ; Mon, 3 Aug 2009 20:18:48 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -1.799 X-Spam-Level: X-Spam-Status: No, score=-1.799 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, L_P0F_UNKN=0.8] X-Amavis-OS-Fingerprint: UNKNOWN [S4:42:1:60:M1460,S,T,N,W4:.:?:?] (up: 4210 hrs), (link: ethernet/modem), [85.214.61.233] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZH2oQlovnsi4 for ; Mon, 3 Aug 2009 20:18:42 +0000 (GMT) Received: from jsschmid.de (jsschmid.de [85.214.61.233]) by menubar.gnome.org (Postfix) with ESMTP id 0515A7500C6 for ; Mon, 3 Aug 2009 20:18:33 +0000 (GMT) Received: from [192.168.1.139] (ppp-88-217-109-215.dynamic.mnet-online.de [88.217.109.215]) by jsschmid.de (Postfix) with ESMTP id 1FA7E9CD0BC; Mon, 3 Aug 2009 20:18:30 +0000 (UTC) From: Johannes Schmid To: bas.driessen@xobas.com In-Reply-To: <1249298356.31893.32.camel@ams.xobas.net> References: <1248956551.4329.4.camel@ams.xobas.net> <1249298356.31893.32.camel@ams.xobas.net> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-uqIFOIByLO4xj3XcFMwh" Date: Mon, 03 Aug 2009 22:18:29 +0200 Message-Id: <1249330709.4052.2.camel@Obelix> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Cc: GNOME-DB List , Vivien Malerba Subject: Re: [gnome-db] Meta Store issue with MySQL. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 20:18:48 -0000 --=-uqIFOIByLO4xj3XcFMwh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi! > As a rollback is triggered, the meta store is empty. >=20 > I have no idea if I am pretty close to have this all working, or if > this whole area is still up for a re-write/under development. >=20 > See also my previous thread for a reproducible case of this issue. >=20 > Any comments/tips/hints? >=20 You can quite easily find out when the first assertion/warning occurs by passing the --g-fatal-warnings command line option to your test-case and starting it in gdb. This will abort the program on the first GError* warning. Looks like these warnings come from some loop. Just in case it is a problem with your code - you need to pass a NULL gerror to any call to avoid this warning. Regards, Johannes --=-uqIFOIByLO4xj3XcFMwh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkp3RhIACgkQAvZZn2XJ+bPVZQCdGu9WgE9LSDr6GVfqTnP6bVDp tVMAnAiCaka7sGQxc8On7NYt9g8GWJIQ =xA2N -----END PGP SIGNATURE----- --=-uqIFOIByLO4xj3XcFMwh-- From bas.driessen@xobas.com Tue Aug 4 11:12:20 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 3690075021A for ; Tue, 4 Aug 2009 11:12:20 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 80 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmAbW-a0jVly for ; Tue, 4 Aug 2009 11:12:11 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 66F9A75021B for ; Tue, 4 Aug 2009 11:12:02 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n74B8ie1023836 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 4 Aug 2009 21:08:47 +1000 From: Bas Driessen To: Vivien Malerba In-Reply-To: <1249298356.31893.32.camel@ams.xobas.net> References: <1248956551.4329.4.camel@ams.xobas.net> <1249298356.31893.32.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-/PUHVcqWFWT1p5OyQIxo" Organization: Xobas Software Date: Tue, 04 Aug 2009 21:08:43 +1000 Message-Id: <1249384123.3139.133.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9650/Tue Aug 4 13:42:34 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] Meta Store issue with MySQL. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 11:12:20 -0000 --=-/PUHVcqWFWT1p5OyQIxo Content-Type: text/plain Content-Transfer-Encoding: 7bit On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote: > On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote: > > > > > > > 2009/7/30 Bas Driessen > > > > > > > 2009/7/30 Bas Driessen > > > > > >> Hello, > > >> > > >> My database is in MySQL. When I run the following command > > to rebuild the > > >> MetaStore (which lives in a sqlite3 database): > > >> > > >> gda_connection_update_meta_store(connection, NULL, > > &error) > > >> > > >> I get the following error/warning: > > >> > > >> ** (process:22406): WARNING **: (+5): Wrong Holder value > > type, expected > > >> type 'boolean' when value's type is 'string' (Provider > > ThreadWrapper) > > >> > > >> > > >> and the MySQL table information is not in the MetaStore. > > In fact if I > > >> do: > > >> > > >> select * from _tables; > > >> > > >> nothing shows up. > > >> > > >> Anyone else having this problem? > > >> > > > > > > The reason for this error is that a SELECT statement > > internally run by the > > > MySQL provider to get meta data returned a column of type > > string instead > > > to > > > a boolean. To solve this, the correction consists in > > locating the faulty > > > SELECT, and use > > gda_connection_statement_execute_select_full() with an > > > array > > > of expected types for the columns instead of > > > gda_connection_statement_execute_select(). This is already > > done at several > > > places in gda-mysql-meta.c. > > > > > > If you want to try to correct it, and if you are in the > > master branch, you > > > can use the definitions in > > > libgda/providers-support/gda-meta-column-types.h > > > (which is dynamically generated). > > > > > > Otherwise, I'd need to have more information to correct > > the problem > > > myself. > > > > > > OK, I will try to locate and correct the issue in libgda. > > Just wanted to > > have confirmed first that this is an issue in libgda and not > > in my setup. > > > > > > To help you, you can uncomment the line 2324 of the gda-meta-store.c > > file, so you'll get debug info about all the results the provider is > > returning for the meta store. > > > OK, I am a step further in this (I think). In file > providers/mysql/gda-mysql-meta.c, line 717 the structure should be > changed from: > > GType col_types_views[] = { > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > G_TYPE_STRING, > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE > }; > > to: > > > GType col_types_views[] = { > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > G_TYPE_STRING, > G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE > }; > > The original error will be gone and it will continue past the point > where it stopped. However, there are now many new error messages: > > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is > NULL before it's set. > The overwriting error message was: Type gchararray not mapped for > value 0 > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is > NULL before it's set. > The overwriting error message was: Type gint not mapped for value > (null) > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is > NULL before it's set. > The overwriting error message was: Invalid column bind data type. 253 > > (this repeats many many times) > ============ > > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is > NULL before it's set. > The overwriting error message was: Unable to get value for row 0 and > column 10 > > ** (process:8055): WARNING **: Type gint not mapped for value (null) > (Provider ThreadWrapper) > > As a rollback is triggered, the meta store is empty. > > I have no idea if I am pretty close to have this all working, or if > this whole area is still up for a re-write/under development. > > See also my previous thread for a reproducible case of this issue. > > Any comments/tips/hints? Vivien, You should have received a patch from Carlos that correct the issues with the MetaStore for the MySQL provider as discussed above. He sent me the patch as well and initial testing shows that the MetaStore builds OK now. Both full update as partial update works OK. It has my thumbs up to be applied to the master. Thanks, Bas. --=-/PUHVcqWFWT1p5OyQIxo Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote:
On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote:


2009/7/30 Bas Driessen <bas.driessen@xobas.com>

> 2009/7/30 Bas Driessen <bas.driessen@xobas.com>
>
>>  Hello,
>>
>> My database is in MySQL. When I run the following command to rebuild the
>> MetaStore (which lives in a sqlite3 database):
>>
>> gda_connection_update_meta_store(connection, NULL, &error)
>>
>> I get the following error/warning:
>>
>> ** (process:22406): WARNING **: (+5): Wrong Holder value type, expected
>> type 'boolean' when value's type is 'string' (Provider ThreadWrapper)
>>
>>
>> and the MySQL table information is not in the MetaStore. In fact if I
>> do:
>>
>> select * from _tables;
>>
>> nothing shows up.
>>
>> Anyone else having this problem?
>>
>
> The reason for this error is that a SELECT statement internally run by the
> MySQL provider to get meta data returned a column of type string instead
> to
> a boolean. To solve this, the correction consists in locating the faulty
> SELECT, and use gda_connection_statement_execute_select_full() with an
> array
> of expected types for the columns instead of
> gda_connection_statement_execute_select(). This is already done at several
> places in gda-mysql-meta.c.
>
> If you want to try to correct it, and if you are in the master branch, you
> can use the definitions in
> libgda/providers-support/gda-meta-column-types.h
> (which is dynamically generated).
>
> Otherwise, I'd need to have more information to correct the problem
> myself.


OK, I will try to locate and correct the issue in libgda. Just wanted to
have confirmed first that this is an issue in libgda and not in my setup.

To help you, you can uncomment the line 2324 of the gda-meta-store.c file, so you'll get debug info about all the results the provider is returning for the meta store.

OK, I am a step further in this (I think). In file providers/mysql/gda-mysql-meta.c, line 717 the structure should be changed from:

GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE
        };

to:


GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE
        };

The original error will be gone and it will continue past the point where it stopped. However, there are now many new error messages:


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gchararray not mapped for value 0

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gint not mapped for value (null)

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Invalid column bind data type. 253

(this repeats many many times)
============


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Unable to get value for row 0 and column 10

** (process:8055): WARNING **: Type gint not mapped for value (null) (Provider ThreadWrapper)

As a rollback is triggered, the meta store is empty.

I have no idea if I am pretty close to have this all working, or if this whole area is still up for a re-write/under development.

See also my previous thread for a reproducible case of this issue.

Any comments/tips/hints?
Vivien,

You should have received a patch from Carlos that correct the issues with the MetaStore for the MySQL provider as discussed above. He sent me the patch as well and initial testing shows that the MetaStore builds OK now. Both full update as partial update works OK. It has my thumbs up to be applied to the master.

Thanks,
Bas.

--=-/PUHVcqWFWT1p5OyQIxo-- From vmalerba@gmail.com Wed Aug 5 09:41:18 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 0639F7500A9 for ; Wed, 5 Aug 2009 09:41:18 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 8898 hrs), (distance 14, link: ethernet/modem), [209.85.220.211] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q96k5bTLezur for ; Wed, 5 Aug 2009 09:41:12 +0000 (GMT) Received: from mail-fx0-f211.google.com (mail-fx0-f211.google.com [209.85.220.211]) by menubar.gnome.org (Postfix) with ESMTP id 2C278750070 for ; Wed, 5 Aug 2009 09:41:02 +0000 (GMT) Received: by fxm7 with SMTP id 7so3627948fxm.34 for ; Wed, 05 Aug 2009 02:41:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=6/bS0vE+CLgof+ZGDRdfQCh5ezP4XTEqOLfqQsvgxb8=; b=f4WtAZzFTw+ciNzSkIcy4Jw9JKBH5bMlIf8cr8EeVeasbxijZ4Ma7bZPan9hZnLLQd K8SnEymXAQUAmi34AZylU0Vg2j6BTd1PqSGkWD3JTXf5C3wY2pEHhO0T3FeAofqYWuFh uToeTFarws/LWEJt0aJEO0arrV3Zqvb8D78yQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TJWIaXIB+JmwZZQo9+d2ei6eAfQWVwoDU0cDpWI2CTk0FxTja91idcdYtZfFLWqMxW pLk0VeQIv6f8edAQlmHWCMl0E7lz5kpuerc1tT6d3eERcN+Tu1981a9ldtjR3HSltspH +xq2Rf0xueC21LueJyY604LXHPef5s4/1dXdU= MIME-Version: 1.0 Received: by 10.103.197.17 with SMTP id z17mr698073mup.134.1249465260277; Wed, 05 Aug 2009 02:41:00 -0700 (PDT) In-Reply-To: <1249384123.3139.133.camel@ams.xobas.net> References: <1248956551.4329.4.camel@ams.xobas.net> <1249298356.31893.32.camel@ams.xobas.net> <1249384123.3139.133.camel@ams.xobas.net> Date: Wed, 5 Aug 2009 11:41:00 +0200 Message-ID: From: Vivien Malerba To: bas.driessen@xobas.com Content-Type: multipart/alternative; boundary=0016e659fc5aff8261047061cc1b Cc: GNOME-DB List Subject: Re: [gnome-db] Meta Store issue with MySQL. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 09:41:18 -0000 --0016e659fc5aff8261047061cc1b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 2009/8/4 Bas Driessen > On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote: > > On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote: > > > > 2009/7/30 Bas Driessen > > > > 2009/7/30 Bas Driessen > > > >> Hello, > >> > >> My database is in MySQL. When I run the following command to rebuild the > >> MetaStore (which lives in a sqlite3 database): > >> > >> gda_connection_update_meta_store(connection, NULL, &error) > >> > >> I get the following error/warning: > >> > >> ** (process:22406): WARNING **: (+5): Wrong Holder value type, expected > >> type 'boolean' when value's type is 'string' (Provider ThreadWrapper) > >> > >> > >> and the MySQL table information is not in the MetaStore. In fact if I > >> do: > >> > >> select * from _tables; > >> > >> nothing shows up. > >> > >> Anyone else having this problem? > >> > > > > The reason for this error is that a SELECT statement internally run by > the > > MySQL provider to get meta data returned a column of type string instead > > to > > a boolean. To solve this, the correction consists in locating the faulty > > SELECT, and use gda_connection_statement_execute_select_full() with an > > array > > of expected types for the columns instead of > > gda_connection_statement_execute_select(). This is already done at > several > > places in gda-mysql-meta.c. > > > > If you want to try to correct it, and if you are in the master branch, > you > > can use the definitions in > > libgda/providers-support/gda-meta-column-types.h > > (which is dynamically generated). > > > > Otherwise, I'd need to have more information to correct the problem > > myself. > > > OK, I will try to locate and correct the issue in libgda. Just wanted to > have confirmed first that this is an issue in libgda and not in my setup. > > > To help you, you can uncomment the line 2324 of the gda-meta-store.c file, > so you'll get debug info about all the results the provider is returning for > the meta store. > > > OK, I am a step further in this (I think). In file > providers/mysql/gda-mysql-meta.c, line 717 the structure should be changed > from: > > GType col_types_views[] = { > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > G_TYPE_STRING, *G_TYPE_STRING*, G_TYPE_NONE > }; > > to: > > > GType col_types_views[] = { > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > G_TYPE_STRING, *G_TYPE_BOOLEAN*, G_TYPE_NONE > }; > > The original error will be gone and it will continue past the point where > it stopped. However, there are now many new error messages: > > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is NULL > before it's set. > The overwriting error message was: Type gchararray not mapped for value 0 > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is NULL > before it's set. > The overwriting error message was: Type gint not mapped for value (null) > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is NULL > before it's set. > The overwriting error message was: Invalid column bind data type. 253 > > (this repeats many many times) > ============ > > > (process:8055): GLib-WARNING **: GError set over the top of a previous > GError or uninitialized memory. > This indicates a bug in someone's code. You must ensure an error is NULL > before it's set. > The overwriting error message was: Unable to get value for row 0 and column > 10 > > ** (process:8055): WARNING **: Type gint not mapped for value (null) > (Provider ThreadWrapper) > > As a rollback is triggered, the meta store is empty. > > I have no idea if I am pretty close to have this all working, or if this > whole area is still up for a re-write/under development. > > See also my previous thread for a reproducible case of this issue. > > Any comments/tips/hints? > > Vivien, > > You should have received a patch from Carlos that correct the issues with > the MetaStore for the MySQL provider as discussed above. He sent me the > patch as well and initial testing shows that the MetaStore builds OK now. > Both full update as partial update works OK. It has my thumbs up to be > applied to the master. > Ok, then I propose you apply it yourself, as I'm currently on holliday with limited internet access. Thanks a lot to you and Carlos, Vivien > > > Thanks, > Bas. > > --0016e659fc5aff8261047061cc1b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/8/4 Bas Driessen = <bas.driessen@xobas.com>= ;
=20 =20
On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote:
On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote:


2009/7/30 Bas Driessen <bas.driessen@xobas.com>

> 2009/7/30 Bas Driessen <bas.driessen@xobas.com>
>
>> =A0Hello,
>>
>> My database is in MySQL. When I run the following comm= and to rebuild the
>> MetaStore (which lives in a sqlite3 database):
>>
>> gda_connection_update_meta_store(connection, NULL, &am= p;error)
>>
>> I get the following error/warning:
>>
>> ** (process:22406): WARNING **: (+5): Wrong Holder val= ue type, expected
>> type 'boolean' when value's type is 's= tring' (Provider ThreadWrapper)
>>
>>
>> and the MySQL table information is not in the MetaStor= e. In fact if I
>> do:
>>
>> select * from _tables;
>>
>> nothing shows up.
>>
>> Anyone else having this problem?
>>
>
> The reason for this error is that a SELECT statement inter= nally run by the
> MySQL provider to get meta data returned a column of type = string instead
> to
> a boolean. To solve this, the correction consists in locat= ing the faulty
> SELECT, and use gda_connection_statement_execute_select_fu= ll() with an
> array
> of expected types for the columns instead of
> gda_connection_statement_execute_select(). This is already= done at several
> places in gda-mysql-meta.c.
>
> If you want to try to correct it, and if you are in the ma= ster branch, you
> can use the definitions in
> libgda/providers-support/gda-meta-column-types.h
> (which is dynamically generated).
>
> Otherwise, I'd need to have more information to correc= t the problem
> myself.


OK, I will try to locate and correct the issue in libgda. Just = wanted to
have confirmed first that this is an issue in libgda and not in= my setup.

To help you, you can uncomment the line 2324 of the gda-meta-store.= c file, so you'll get debug info about all the results the provider is = returning for the meta store.

OK, I am a step further in this (I think). In file providers/mysql/gda-= mysql-meta.c, line 717 the structure should be changed from:

GType col_types_views[] =3D {
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 G_TYPE_STRING, G_TYPE_STR= ING, G_TYPE_STRING, G_TYPE_STRING,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 G_TYPE_STRING, G_TYPE_= STRING, G_TYPE_NONE
=A0=A0=A0=A0=A0=A0=A0 };

to:


GType col_types_views[] =3D {
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 G_TYPE_STRING, G_TYPE_STR= ING, G_TYPE_STRING, G_TYPE_STRING,
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 G_TYPE_STRING, G_TYPE_= BOOLEAN, G_TYPE_NONE
=A0=A0=A0=A0=A0=A0=A0 };

The original error will be gone and it will continue past the point whe= re it stopped. However, there are now many new error messages:


(process:8055): GLib-WARNING **: GError set over the top of a previous = GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is= NULL before it's set.
The overwriting error message was: Type gchararray not mapped for value= 0

(process:8055): GLib-WARNING **: GError set over the top of a previous = GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is= NULL before it's set.
The overwriting error message was: Type gint not mapped for value (null= )

(process:8055): GLib-WARNING **: GError set over the top of a previous = GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is= NULL before it's set.
The overwriting error message was: Invalid column bind data type. 253
(this repeats many many times)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


(process:8055): GLib-WARNING **: GError set over the top of a previous = GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is= NULL before it's set.
The overwriting error message was: Unable to get value for row 0 and co= lumn 10

** (process:8055): WARNING **: Type gint not mapped for value (null) (P= rovider ThreadWrapper)

As a rollback is triggered, the meta store is empty.

I have no idea if I am pretty close to have this all working, or if thi= s whole area is still up for a re-write/under development.

See also my previous thread for a reproducible case of this issue.

Any comments/tips/hints?
Vivien,

You should have received a patch from Carlos that correct the issues with t= he MetaStore for the MySQL provider as discussed above. He sent me the patc= h as well and initial testing shows that the MetaStore builds OK now. Both = full update as partial update works OK. It has my thumbs up to be applied t= o the master.

Ok, then I propose you apply it yourself, as I'm = currently on holliday with limited internet access.
Thanks a lot to you = and Carlos,

Vivien


Thanks,
Bas.


--0016e659fc5aff8261047061cc1b-- From bas.driessen@xobas.com Wed Aug 5 11:30:30 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id EE6C4750206 for ; Wed, 5 Aug 2009 11:30:29 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 141 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVfJLYppDBNE for ; Wed, 5 Aug 2009 11:30:23 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id CAA2475006C for ; Wed, 5 Aug 2009 11:30:14 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n75BTxJ0011545 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 5 Aug 2009 21:30:05 +1000 From: Bas Driessen To: Vivien Malerba In-Reply-To: References: <1248956551.4329.4.camel@ams.xobas.net> <1249298356.31893.32.camel@ams.xobas.net> <1249384123.3139.133.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-NjHO9boHp1M4hAPfVmeM" Organization: Xobas Software Date: Wed, 05 Aug 2009 21:29:53 +1000 Message-Id: <1249471793.3351.1.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9656/Wed Aug 5 13:37:12 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] Meta Store issue with MySQL. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 11:30:30 -0000 --=-NjHO9boHp1M4hAPfVmeM Content-Type: text/plain Content-Transfer-Encoding: 7bit On Wed, 2009-08-05 at 11:41 +0200, Vivien Malerba wrote: > > > > 2009/8/4 Bas Driessen > > > On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote: > > > On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote: > > > > > > > > > > > 2009/7/30 Bas Driessen > > > > > > > > > > 2009/7/30 Bas Driessen > > > > > > > >> Hello, > > > >> > > > >> My database is in MySQL. When I run the > > > following command to rebuild the > > > >> MetaStore (which lives in a sqlite3 database): > > > >> > > > >> gda_connection_update_meta_store(connection, > > > NULL, &error) > > > >> > > > >> I get the following error/warning: > > > >> > > > >> ** (process:22406): WARNING **: (+5): Wrong > > > Holder value type, expected > > > >> type 'boolean' when value's type is > > > 'string' (Provider ThreadWrapper) > > > >> > > > >> > > > >> and the MySQL table information is not in the > > > MetaStore. In fact if I > > > >> do: > > > >> > > > >> select * from _tables; > > > >> > > > >> nothing shows up. > > > >> > > > >> Anyone else having this problem? > > > >> > > > > > > > > The reason for this error is that a SELECT > > > statement internally run by the > > > > MySQL provider to get meta data returned a > > > column of type string instead > > > > to > > > > a boolean. To solve this, the correction > > > consists in locating the faulty > > > > SELECT, and use > > > gda_connection_statement_execute_select_full() > > > with an > > > > array > > > > of expected types for the columns instead of > > > > gda_connection_statement_execute_select(). This > > > is already done at several > > > > places in gda-mysql-meta.c. > > > > > > > > If you want to try to correct it, and if you are > > > in the master branch, you > > > > can use the definitions in > > > > libgda/providers-support/gda-meta-column-types.h > > > > (which is dynamically generated). > > > > > > > > Otherwise, I'd need to have more information to > > > correct the problem > > > > myself. > > > > > > > > > OK, I will try to locate and correct the issue in > > > libgda. Just wanted to > > > have confirmed first that this is an issue in > > > libgda and not in my setup. > > > > > > > > > To help you, you can uncomment the line 2324 of the > > > gda-meta-store.c file, so you'll get debug info about all > > > the results the provider is returning for the meta store. > > > > > > OK, I am a step further in this (I think). In file > > providers/mysql/gda-mysql-meta.c, line 717 the structure > > should be changed from: > > > > GType col_types_views[] = { > > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > > G_TYPE_STRING, > > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE > > }; > > > > to: > > > > > > GType col_types_views[] = { > > G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, > > G_TYPE_STRING, > > G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE > > }; > > > > The original error will be gone and it will continue past > > the point where it stopped. However, there are now many new > > error messages: > > > > > > (process:8055): GLib-WARNING **: GError set over the top of > > a previous GError or uninitialized memory. > > This indicates a bug in someone's code. You must ensure an > > error is NULL before it's set. > > The overwriting error message was: Type gchararray not > > mapped for value 0 > > > > (process:8055): GLib-WARNING **: GError set over the top of > > a previous GError or uninitialized memory. > > This indicates a bug in someone's code. You must ensure an > > error is NULL before it's set. > > The overwriting error message was: Type gint not mapped for > > value (null) > > > > (process:8055): GLib-WARNING **: GError set over the top of > > a previous GError or uninitialized memory. > > This indicates a bug in someone's code. You must ensure an > > error is NULL before it's set. > > The overwriting error message was: Invalid column bind data > > type. 253 > > > > (this repeats many many times) > > ============ > > > > > > (process:8055): GLib-WARNING **: GError set over the top of > > a previous GError or uninitialized memory. > > This indicates a bug in someone's code. You must ensure an > > error is NULL before it's set. > > The overwriting error message was: Unable to get value for > > row 0 and column 10 > > > > ** (process:8055): WARNING **: Type gint not mapped for > > value (null) (Provider ThreadWrapper) > > > > As a rollback is triggered, the meta store is empty. > > > > I have no idea if I am pretty close to have this all > > working, or if this whole area is still up for a > > re-write/under development. > > > > See also my previous thread for a reproducible case of this > > issue. > > > > Any comments/tips/hints? > > Vivien, > > You should have received a patch from Carlos that correct the > issues with the MetaStore for the MySQL provider as discussed > above. He sent me the patch as well and initial testing shows > that the MetaStore builds OK now. Both full update as partial > update works OK. It has my thumbs up to be applied to the > master. > > Ok, then I propose you apply it yourself, as I'm currently on holliday > with limited internet access. > Thanks a lot to you and Carlos, > > Vivien > > Roger that, will do. Enjoy your holiday and drop us a line when you are back in the captains chair :) Bas. --=-NjHO9boHp1M4hAPfVmeM Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Wed, 2009-08-05 at 11:41 +0200, Vivien Malerba wrote:


2009/8/4 Bas Driessen <bas.driessen@xobas.com>

On Mon, 2009-08-03 at 21:19 +1000, Bas Driessen wrote:
On Thu, 2009-07-30 at 16:17 +0200, Vivien Malerba wrote:


2009/7/30 Bas Driessen <bas.driessen@xobas.com>

> 2009/7/30 Bas Driessen <bas.driessen@xobas.com>
>
>>  Hello,
>>
>> My database is in MySQL. When I run the following command to rebuild the
>> MetaStore (which lives in a sqlite3 database):
>>
>> gda_connection_update_meta_store(connection, NULL, &error)
>>
>> I get the following error/warning:
>>
>> ** (process:22406): WARNING **: (+5): Wrong Holder value type, expected
>> type 'boolean' when value's type is 'string' (Provider ThreadWrapper)
>>
>>
>> and the MySQL table information is not in the MetaStore. In fact if I
>> do:
>>
>> select * from _tables;
>>
>> nothing shows up.
>>
>> Anyone else having this problem?
>>
>
> The reason for this error is that a SELECT statement internally run by the
> MySQL provider to get meta data returned a column of type string instead
> to
> a boolean. To solve this, the correction consists in locating the faulty
> SELECT, and use gda_connection_statement_execute_select_full() with an
> array
> of expected types for the columns instead of
> gda_connection_statement_execute_select(). This is already done at several
> places in gda-mysql-meta.c.
>
> If you want to try to correct it, and if you are in the master branch, you
> can use the definitions in
> libgda/providers-support/gda-meta-column-types.h
> (which is dynamically generated).
>
> Otherwise, I'd need to have more information to correct the problem
> myself.


OK, I will try to locate and correct the issue in libgda. Just wanted to
have confirmed first that this is an issue in libgda and not in my setup.

To help you, you can uncomment the line 2324 of the gda-meta-store.c file, so you'll get debug info about all the results the provider is returning for the meta store.

OK, I am a step further in this (I think). In file providers/mysql/gda-mysql-meta.c, line 717 the structure should be changed from:

GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_NONE
        };

to:


GType col_types_views[] = {
                G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING, G_TYPE_STRING,
                G_TYPE_STRING, G_TYPE_BOOLEAN, G_TYPE_NONE
        };

The original error will be gone and it will continue past the point where it stopped. However, there are now many new error messages:


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gchararray not mapped for value 0

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Type gint not mapped for value (null)

(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Invalid column bind data type. 253

(this repeats many many times)
============


(process:8055): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Unable to get value for row 0 and column 10

** (process:8055): WARNING **: Type gint not mapped for value (null) (Provider ThreadWrapper)

As a rollback is triggered, the meta store is empty.

I have no idea if I am pretty close to have this all working, or if this whole area is still up for a re-write/under development.

See also my previous thread for a reproducible case of this issue.

Any comments/tips/hints?
Vivien,

You should have received a patch from Carlos that correct the issues with the MetaStore for the MySQL provider as discussed above. He sent me the patch as well and initial testing shows that the MetaStore builds OK now. Both full update as partial update works OK. It has my thumbs up to be applied to the master.

Ok, then I propose you apply it yourself, as I'm currently on holliday with limited internet access.
Thanks a lot to you and Carlos,

Vivien


Roger that, will do. Enjoy your holiday and drop us a line when you are back in the captains chair :)

Bas.

--=-NjHO9boHp1M4hAPfVmeM-- From esodan@gmail.com Wed Aug 5 23:08:29 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 26A2775012B for ; Wed, 5 Aug 2009 23:08:29 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (firewall!) (up: 10282 hrs), (distance 13, link: (Google 2)), [209.85.198.232] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPMkjf9JMUKC for ; Wed, 5 Aug 2009 23:08:21 +0000 (GMT) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by menubar.gnome.org (Postfix) with ESMTP id 1870D75016A for ; Wed, 5 Aug 2009 23:08:12 +0000 (GMT) Received: by rv-out-0506.google.com with SMTP id b25so144428rvf.3 for ; Wed, 05 Aug 2009 16:08:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=j8cHEK4c0x2VCfdNgzxYtM8PjXAomlJMVNkhSkM2/BU=; b=SboU5zTgk2zPrILpRQR8hoXPCi+mDnGVgfFTIPeVRiuPeCbh8UA3ca7wlHpBTrBJwl If+HySdqwxJ5yqKzaSt8H6bXGWNk92H8I5+Bv3zqWmz42ghhAqyHX+aIjHyynWAJLAW9 wlYv6/FSe0sCj95ORlXTAg7ZUKMpHAr+KTixg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=LbFZm78tC9TOAdOSv/Y31VAgt9ZpfjWuDedrH6f0q5gt5Ev09U7+XqXJTUdElGPiFl HgwOcEfUOeAtgnzKRzh9xocUTe97Vd2vHtcWu5yrQ7YFTDeTYKnaTsmnO8qjO0a9Dcb5 KP66hM5+Q98+Augnb4kP3r6lOzKVnw+aLXi/c= MIME-Version: 1.0 Received: by 10.140.193.20 with SMTP id q20mr16858rvf.70.1249513691011; Wed, 05 Aug 2009 16:08:11 -0700 (PDT) Date: Wed, 5 Aug 2009 18:08:11 -0500 Message-ID: <144160610908051608l481f56abh551b93a52979975f@mail.gmail.com> From: Daniel Espinosa To: gnome-db-list@gnome.org Content-Type: multipart/alternative; boundary=000e0cd29a6ab1db7d04706d138b Subject: [gnome-db] Patch for GObjectIntrospection Status X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 23:08:29 -0000 --000e0cd29a6ab1db7d04706d138b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Have some one know what happend about the status of following bugs reports in order to get GObject Instrospection? 585351 585706 --=20 Trabajar, la mejor arma para tu superaci=C3=B3n "de grano en grano, se hace la arena" (R) (en tr=C3=A1mite, pero para los c= uates: LIBRE --000e0cd29a6ab1db7d04706d138b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Have some one know what happend about the status of following bugs reports = in order to get GObject Instrospection?

585351
= 585706

--
Trabajar, la mejor arma para tu supe= raci=C3=B3n
"de grano en grano, se hace la arena" (R) (en tr= =C3=A1mite, pero para los cuates: LIBRE
--000e0cd29a6ab1db7d04706d138b-- From azagli@libero.it Mon Aug 10 17:00:55 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 57C707500FF for ; Mon, 10 Aug 2009 17:00:55 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -0.74 X-Spam-Level: X-Spam-Status: No, score=-0.74 tagged_above=-999 required=2 tests=[BAYES_20=-0.74] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 3) (NAT!) (up: 3738 hrs), (distance 23, link: GPRS, T1, FreeS/WAN), [212.52.84.107] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DvQU9aQebH1v for ; Mon, 10 Aug 2009 17:00:49 +0000 (GMT) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by menubar.gnome.org (Postfix) with ESMTP id 06ABC7500DA for ; Mon, 10 Aug 2009 17:00:40 +0000 (GMT) Received: from phobos.saetta.homelinux.org (151.49.10.90) by cp-out7.libero.it (8.5.107) id 4A700F43011B612E for gnome-db-list@gnome.org; Mon, 10 Aug 2009 19:00:38 +0200 Received: from localhost (localhost [127.0.0.1]) by phobos.saetta.homelinux.org (Postfix) with ESMTP id E602A9FB5 for ; Mon, 10 Aug 2009 18:58:59 +0200 (CEST) Received: from 10.0.0.102 ([10.0.0.102]) by 10.0.0.4 (Horde Framework) with HTTP; Mon, 10 Aug 2009 18:58:58 +0200 Message-ID: <20090810185858.16876cjiiloozchs@10.0.0.4> Date: Mon, 10 Aug 2009 18:58:58 +0200 From: Andrea Zagli To: gnome-db-list@gnome.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3.2) Subject: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 17:00:55 -0000 libgda 4.0.1 - provider sqlite (i didn't try with other providers) - =20 sqlite 3.6.16 when i execute this sql select distinct year from customer i get n rows per year instead one only when i execute this sql select * from customers where exists (select orders.* from orders =20 where customers.id =3D orders.id_customers) i get the error =C2=ABnear "(": syntax error=C2=BB both the sql work as i expect if executed inside sqlite console why? i didn't understand thanks in advance From vmalerba@gmail.com Mon Aug 10 19:26:59 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 440B7750177 for ; Mon, 10 Aug 2009 19:26:59 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 11010 hrs), (distance 16, link: ethernet/modem), [209.85.218.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOHYiC4OCloY for ; Mon, 10 Aug 2009 19:26:51 +0000 (GMT) Received: from mail-bw0-f215.google.com (mail-bw0-f215.google.com [209.85.218.215]) by menubar.gnome.org (Postfix) with ESMTP id DA2C9750062 for ; Mon, 10 Aug 2009 19:26:42 +0000 (GMT) Received: by bwz11 with SMTP id 11so2926035bwz.15 for ; Mon, 10 Aug 2009 12:26:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Pm36Z/YCzLKD5R+kIGWmmrN+xuUrGkv7GulnThSucuk=; b=fyv8Vsc2BmiCBXGVJA+L4ocxnGf9uGLYgRO0ZNy2Y/U0QpxJvRbHE8OfowaxpVeQ6H atC5tInASxlUjxNOI7u2g5/JKbAXtB7QmBhnVOxpoScienr6pMxFV2kKsokH3irrQzy5 3yr+dRMqdn7IYi1bti2eWz/4KZRWmbwAtFIyw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GFeCTcmR7v8XNoImaAJ0TA8pup9vTiZ/Z3IAGYILL/g4W56Rp5VATdDnniWiQxeutT 7M8mXUm2XujNULViJ3J/z1fx1I521kA+rvw+prIT86zlDFmf68m7MvWGetyq8LrYAOrH i4x4JrJEpr5w8tFmvAaHWYARLhHH2sTSfIglo= MIME-Version: 1.0 Received: by 10.103.233.11 with SMTP id k11mr761347mur.108.1249932400214; Mon, 10 Aug 2009 12:26:40 -0700 (PDT) In-Reply-To: <20090810185858.16876cjiiloozchs@10.0.0.4> References: <20090810185858.16876cjiiloozchs@10.0.0.4> Date: Mon, 10 Aug 2009 21:26:40 +0200 Message-ID: From: Vivien Malerba To: Andrea Zagli Content-Type: multipart/alternative; boundary=0016369205b5b542d10470ce90f6 Cc: gnome-db-list@gnome.org Subject: Re: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Aug 2009 19:26:59 -0000 --0016369205b5b542d10470ce90f6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2009/8/10 Andrea Zagli > libgda 4.0.1 - provider sqlite (i didn't try with other providers) - sqli= te > 3.6.16 > > > when i execute this sql > > select distinct year from customer > > i get n rows per year instead one only > > > when i execute this sql > > select * from customers where exists (select orders.* from orders where > customers.id =3D orders.id_customers) > > i get the error =ABnear "(": syntax error=BB > > > both the sql work as i expect if executed inside sqlite console > > why? i didn't understand > > thanks in advance > This has been corrected, but is not yet available in a public release, it will be in 4.0.3, see http://git.gnome.org/cgit/libgda/commit/?id=3D26f214fbfbd99ded4b30576999285= c1fb7eba06ffor details. The problem is due to the fact that Libgda adds some extra columns to SELECT statements in SQLite to be able to generate update, inser= t and delete statement when modifying the results of a SELECT and there was a bug in the process. In the meanwhile, you can use Libgda from git or I can send you a tarball with the current sources which will become version 4.0.3. Regards, Vivien > > _______________________________________________ > gnome-db-list mailing list > gnome-db-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-db-list > --0016369205b5b542d10470ce90f6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/8/10 Andrea Zagli <azagli@libero.it>
libgda 4.0.1 - provider sqlite (i didn't try with other providers) - sq= lite 3.6.16


when i execute this sql

select distinct year from customer

i get n rows per year instead one only


when i execute this sql

select * from customers where exists (select orders.* from orders where customers.id =3D orders.= id_customers)

i get the error =ABnear "(": syntax error=BB


both the sql work as i expect if executed inside sqlite console

why? i didn't understand

thanks in advance

This has been corrected, but is not yet available in = a public release, it will be in 4.0.3, see http://g= it.gnome.org/cgit/libgda/commit/?id=3D26f214fbfbd99ded4b30576999285c1fb7eba= 06f for details. The problem is due to the fact that Libgda adds some e= xtra columns to SELECT statements in SQLite to be able to generate update, = insert and delete statement when modifying the results of a SELECT and ther= e was a bug in the process.

In the meanwhile, you can use Libgda from git or I can send you a tarba= ll with the current sources which will become version 4.0.3.

Regards= ,

Vivien
=A0

_______________________________________________
gnome-db-list mailing list
gnome-db-list@= gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-db-list

--0016369205b5b542d10470ce90f6-- From azagli@libero.it Wed Aug 12 07:31:52 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id CA07375013E for ; Wed, 12 Aug 2009 07:31:52 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 3) (NAT!) (up: 3835 hrs), (distance 23, link: GPRS, T1, FreeS/WAN), [212.52.84.110] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdPUNO8qPKlr for ; Wed, 12 Aug 2009 07:31:46 +0000 (GMT) Received: from cp-out10.libero.it (cp-out10.libero.it [212.52.84.110]) by menubar.gnome.org (Postfix) with ESMTP id 23832750075 for ; Wed, 12 Aug 2009 07:31:35 +0000 (GMT) Received: from phobos.saetta.homelinux.org (151.49.17.93) by cp-out10.libero.it (8.5.107) id 4A7587E000D0203B for gnome-db-list@gnome.org; Wed, 12 Aug 2009 09:31:32 +0200 Received: from localhost (localhost [127.0.0.1]) by phobos.saetta.homelinux.org (Postfix) with ESMTP id B82AF9FB0 for ; Wed, 12 Aug 2009 09:27:44 +0200 (CEST) Received: from idefix.comune.scandicci.fi.it (idefix.comune.scandicci.fi.it [159.213.80.210]) by saetta.homelinux.org (Horde Framework) with HTTP; Wed, 12 Aug 2009 09:27:44 +0200 Message-ID: <20090812092744.20021qc4rqqr5on4@saetta.homelinux.org> Date: Wed, 12 Aug 2009 09:27:44 +0200 From: Andrea Zagli To: gnome-db-list@gnome.org References: <20090810185858.16876cjiiloozchs@10.0.0.4> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.2) Subject: Re: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 07:31:53 -0000 Il giorno lun 10 ago 2009 21:26:40 CEST, Vivien Malerba ha scritto: > 2009/8/10 Andrea Zagli > >> libgda 4.0.1 - provider sqlite (i didn't try with other providers) - sqlite >> 3.6.16 >> >> [...] >> > > This has been corrected, but is not yet available in a public release, it > will be in 4.0.3, see > http://git.gnome.org/cgit/libgda/commit/?id=26f214fbfbd99ded4b30576999285c1fb7eba06ffor > details. The problem is due to the fact that Libgda adds some extra > columns to SELECT statements in SQLite to be able to generate update, insert > and delete statement when modifying the results of a SELECT and there was a > bug in the process. sorry for the mistake, but i'm using libgda 4.1.0 and not 4.0.1 as i wrote what you wrote is valid also for that version? From vmalerba@gmail.com Wed Aug 12 13:10:20 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 57E7D750143 for ; Wed, 12 Aug 2009 13:10:20 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 11427 hrs), (distance 16, link: ethernet/modem), [209.85.218.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Tg0TlOCcsWd for ; Wed, 12 Aug 2009 13:10:12 +0000 (GMT) Received: from mail-bw0-f215.google.com (mail-bw0-f215.google.com [209.85.218.215]) by menubar.gnome.org (Postfix) with ESMTP id 89842750117 for ; Wed, 12 Aug 2009 13:10:02 +0000 (GMT) Received: by bwz11 with SMTP id 11so3924588bwz.15 for ; Wed, 12 Aug 2009 06:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=mOzrdWrbTXLu3bX6QsF0WhHdQexppqYpzsh3a/H4kc0=; b=iH3GLLBgGPbAXn926jXWmXGgwQzRJ0mPvfdfimZsOw5r/XLtxeD8L1NWgVR2GDFavl i3fzpGeT9lQZ+nUtUpDOJ5YN74ptH7iLu1+43CtqC2aHORGI9LehSTTXsK7nOKrbs21m L/J3G4fiv6SAzuKyhAs75EFFb946435ZgfYZg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vH/Wc9BhsKzvJ+irJdItjogVClNitEnSWLshy9RjaNEDr1yT1DnljxysYFGwCvWZgD vox16mTgGZSb4ci+Bq68fVjz76FCderOAGaisq8MqXvLR+YbBXNr8Vbh+NKsoJaeW2B+ zPlSZbiSzw3TWlg3ZcmGx/2+q3fmWZai2PYg8= MIME-Version: 1.0 Received: by 10.103.134.4 with SMTP id l4mr33372mun.53.1250082600546; Wed, 12 Aug 2009 06:10:00 -0700 (PDT) In-Reply-To: <20090812092744.20021qc4rqqr5on4@saetta.homelinux.org> References: <20090810185858.16876cjiiloozchs@10.0.0.4> <20090812092744.20021qc4rqqr5on4@saetta.homelinux.org> Date: Wed, 12 Aug 2009 15:10:00 +0200 Message-ID: From: Vivien Malerba To: Andrea Zagli Content-Type: multipart/alternative; boundary=0016364d203558706c0470f18906 Cc: gnome-db-list@gnome.org Subject: Re: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 13:10:20 -0000 --0016364d203558706c0470f18906 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 2009/8/12 Andrea Zagli > Il giorno lun 10 ago 2009 21:26:40 CEST, Vivien Malerba ha scritto: > >> 2009/8/10 Andrea Zagli >> >> libgda 4.0.1 - provider sqlite (i didn't try with other providers) - >>> sqlite >>> 3.6.16 >>> >>> [...] >>> >>> >> This has been corrected, but is not yet available in a public release, it >> will be in 4.0.3, see >> >> http://git.gnome.org/cgit/libgda/commit/?id=26f214fbfbd99ded4b30576999285c1fb7eba06ffor >> details. The problem is due to the fact that Libgda adds some extra >> columns to SELECT statements in SQLite to be able to generate update, >> insert >> and delete statement when modifying the results of a SELECT and there was >> a >> bug in the process. >> > > sorry for the mistake, but i'm using libgda 4.1.0 and not 4.0.1 as i wrote > > what you wrote is valid also for that version? > Yes, the same applies. The correction was made in both the 4.0 and 4.1 (master) branches. Vivien --0016364d203558706c0470f18906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/8/12 Andrea Zagli <azagli@libero.it= >
2009/8/10 Andrea Zagli <azagli@libero.it>

libgda 4.0.1 - provider sqlite (i didn't try with other providers) - sq= lite
3.6.16

[...]


This has been corrected, but is not yet available in a public release, it will be in 4.0.3, see
http://git.gnome.org/cgit/libg= da/commit/?id=3D26f214fbfbd99ded4b30576999285c1fb7eba06ffor
details. The problem is due to the fact that Libgda adds some extra
columns to SELECT statements in SQLite to be able to generate update, inser= t
and delete statement when modifying the results of a SELECT and there was a=
bug in the process.

sorry for the mistake, but i'm using libgda 4.1.0 and not 4.0.1 as i wr= ote

what you wrote is valid also for that version?
Yes, the same applies. The correction was made in bot= h the 4.0 and 4.1 (master) branches.

Vivien


--0016364d203558706c0470f18906-- From bas.driessen@xobas.com Fri Aug 14 11:37:40 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id BC0E1750161 for ; Fri, 14 Aug 2009 11:37:40 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 681 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1phCnD0X6my for ; Fri, 14 Aug 2009 11:37:33 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id B078B75007E for ; Fri, 14 Aug 2009 11:37:24 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n7EBbCeI029106 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 14 Aug 2009 21:37:18 +1000 From: Bas Driessen To: Vivien Malerba Content-Type: multipart/mixed; boundary="=-nOzBpyjrrsrkUDhBGs/Y" Organization: Xobas Software Date: Fri, 14 Aug 2009 21:37:11 +1000 Message-Id: <1250249831.17353.12.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9695/Fri Aug 14 07:08:01 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 11:37:41 -0000 --=-nOzBpyjrrsrkUDhBGs/Y Content-Type: multipart/alternative; boundary="=-cV5HHDqNII2wI7WNE4l5" --=-cV5HHDqNII2wI7WNE4l5 Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi Vivien, You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There is a problem with this that if set and a partial meta store update is performed, the meta store is not updated. If using any of the other GDA_CONNECTION_OPTIONS all works fine. I have attached 2 small c programs to re-produce this issue. The database provider is MySQL, my (test) database is called 'stock' and the DSN is 'mystock' -1 rm /tmp/mysql_meta.db -2 in MySQL: drop table xPartsUC; -3 Run mysql_full (source attached) -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, Description varchar(30)); -5 Run mysql_partial (source attached) -6 sqlite3 /tmp/mysql_meta.db then run: select * from _tables where table_name = '"xPartsUC"'; -7 nothing there. Run mysql_full and the entry is there. On a side note, how do I pass 2 or more GDA_CONNECTION_OPTIONS to gda_connection_open_from_dsn() ? ie, if I want to set GDA_CONNECTION_OPTIONS_THREAD_SAFE and the GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE option? The following appears to work, but there must be a better way. GdaConnectionOptions options = GDA_CONNECTION_OPTIONS_THREADSAFE; options = (GdaConnectionOptions)(options + GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE); gda_connection_open_from_dsn(dsn, NULL, options, NULL); Thanks, Bas. --=-cV5HHDqNII2wI7WNE4l5 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit Hi Vivien,

You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There is a problem with this that if set and a partial meta store update is performed, the meta store is not updated. If using any of the other GDA_CONNECTION_OPTIONS all works fine.

I have attached 2 small c programs to re-produce this issue. The database provider is MySQL, my (test) database is called  'stock' and the DSN is 'mystock'

-1 rm /tmp/mysql_meta.db
-2 in MySQL: drop table xPartsUC;
-3 Run mysql_full (source attached)
-4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, Description varchar(30));
-5 Run mysql_partial (source attached)
-6 sqlite3 /tmp/mysql_meta.db  then run: select * from _tables where table_name = '"xPartsUC"';
-7 nothing there. Run mysql_full and the entry is there.

On a side note, how do I pass 2 or more GDA_CONNECTION_OPTIONS to gda_connection_open_from_dsn() ?

ie, if I want to set GDA_CONNECTION_OPTIONS_THREAD_SAFE and the GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE option?


The following appears to work, but there must be a better way.

GdaConnectionOptions options = GDA_CONNECTION_OPTIONS_THREADSAFE;
options = (GdaConnectionOptions)(options + GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE);
gda_connection_open_from_dsn(dsn, NULL, options, NULL);

Thanks,
Bas.

--=-cV5HHDqNII2wI7WNE4l5-- --=-nOzBpyjrrsrkUDhBGs/Y Content-Disposition: attachment; filename="Makefile" Content-Type: text/x-makefile; name="Makefile"; charset="UTF-8" Content-Transfer-Encoding: 7bit CFLAGS = -Wall -g -DGDA_DISABLE_DEPRECATED `pkg-config --cflags libgda-4.0` LDFLAGS = `pkg-config --libs libgda-4.0` all: mysql_full mysql_partial mysql_full: mysql_full.c $(CC) -o mysql_full mysql_full.c $(CFLAGS) $(LDFLAGS) mysql_partial: mysql_partial.c $(CC) -o mysql_partial mysql_partial.c $(CFLAGS) $(LDFLAGS) clean: rm -f *~ rm -f *.o rm -f mysql_full rm -f mysql_partial --=-nOzBpyjrrsrkUDhBGs/Y Content-Disposition: attachment; filename="mysql_full.c" Content-Type: text/x-csrc; name="mysql_full.c"; charset="UTF-8" Content-Transfer-Encoding: 7bit #include int main (int argc, char *argv[]) { GdaConnection* connection; GError* error = NULL; GdaMetaStore *store; gda_init(); error = NULL; /* open connection */ printf("Start.\n"); printf("Open connection.\n"); // connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_NONE, &error); connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_THREAD_SAFE, &error); // connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE, &error); if (!connection) { fprintf (stderr, "%s\n", error->message); return -1; } /* Open Meta Store */ printf("Open Meta Store.\n"); store = gda_meta_store_new_with_file("/tmp/mysql_meta.db"); g_object_set(G_OBJECT(connection), "meta-store", store, NULL); if (!store) { printf("Can not open store.\n"); return -1; } /* Build Complete store */ printf("Build complete store.\n"); if (!gda_connection_update_meta_store(connection, NULL, &error)) { fprintf (stderr, "%s\n", error->message); return -1; } /* The End */ printf("End.\n"); return 0; } --=-nOzBpyjrrsrkUDhBGs/Y Content-Disposition: attachment; filename="mysql_partial.c" Content-Type: text/x-csrc; name="mysql_partial.c"; charset="UTF-8" Content-Transfer-Encoding: 7bit #include int main (int argc, char *argv[]) { GdaConnection* connection; GError* error = NULL; GdaMetaStore *store; gchar *tableName; GdaMetaContext mcontext = {"_tables", 1, NULL, NULL}; gda_init(); error = NULL; /* open connection */ printf("Start.\n"); printf("Open connection.\n"); connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_THREAD_SAFE, &error); // connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE, &error); // connection = gda_connection_open_from_dsn ("mystock", NULL, GDA_CONNECTION_OPTIONS_NONE, &error); if (!connection) { fprintf (stderr, "%s\n", error->message); return -1; } /* Open Meta Store */ printf("Open Meta Store.\n"); store = gda_meta_store_new_with_file("/tmp/mysql_meta.db"); g_object_set(G_OBJECT(connection), "meta-store", store, NULL); if (!store) { printf("Can not open store.\n"); return -1; } /* Update store for just a SINGLE table */ printf("Update Meta Store with SINGLE table.\n"); mcontext.column_names = g_new (gchar *, 1); mcontext.column_names[0] = "table_name"; mcontext.column_values = g_new (GValue *, 1); tableName = gda_sql_identifier_quote("xPartsUC", connection, NULL, TRUE, FALSE); g_value_set_string ((mcontext.column_values[0] = gda_value_new(G_TYPE_STRING)), tableName); g_free(tableName); if (!gda_connection_update_meta_store(connection, &mcontext, &error)) { fprintf (stderr, "%s\n", error->message); return -1; } /* Clean up */ gda_value_free (mcontext.column_values[0]); /* The End */ printf("End.\n"); return 0; } --=-nOzBpyjrrsrkUDhBGs/Y-- From bas.driessen@xobas.com Sat Aug 22 00:42:24 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 443AC7500D0 for ; Sat, 22 Aug 2009 00:42:24 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 1134 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpSU+jjDSG1D for ; Sat, 22 Aug 2009 00:42:17 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id F23177500B9 for ; Sat, 22 Aug 2009 00:42:08 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n7M0ftwu001655 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 21 Aug 2009 20:42:03 -0400 From: Bas Driessen To: Vivien Malerba Content-Type: multipart/alternative; boundary="=-yvsQL6eqShkAujoOcT0N" Organization: Xobas Software Date: Sat, 22 Aug 2009 10:41:55 +1000 Message-Id: <1250901715.28019.1.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9724/Thu Aug 20 23:27:53 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: [gnome-db] 4.1.1 release request. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Aug 2009 00:42:24 -0000 --=-yvsQL6eqShkAujoOcT0N Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi Vivien, There have been many recent changes in libgda master. Is it possible to cut a 4.1.1 release? Thanks, Bas. --=-yvsQL6eqShkAujoOcT0N Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit Hi Vivien,

There have been many recent changes in libgda master. Is it possible to cut a 4.1.1 release?

Thanks,
Bas.

--=-yvsQL6eqShkAujoOcT0N-- From vmalerba@gmail.com Mon Aug 24 07:31:27 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 48320750080 for ; Mon, 24 Aug 2009 07:31:27 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 2416 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsyDVqo+Xt1V for ; Mon, 24 Aug 2009 07:31:21 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id 45906750065 for ; Mon, 24 Aug 2009 07:31:12 +0000 (GMT) Received: by fxm11 with SMTP id 11so1447117fxm.15 for ; Mon, 24 Aug 2009 00:31:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=pNweHoyBYy1jCAdUFkirPbJeCUi0VeXmmkzeiJl/CMM=; b=aTRO7wM6SRDf7+HkRLQ6+j/LX1S+P8ehAh474m+H4CwM8NBq1pSH9J96eUq9tkhMxV eGrPvAtoOVnn3QssWx7kL4n4Kg9hfp7Hd0kENXlhesOTVleTSpa/x/Wrz6tii+BLzmy6 sCACd0XRXJYy8ebpF2ZIAcfH8ucL49YvxSSgs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d3QjYm7/JHqLI5LKPJRm4KB2QXjoWinbixU8Q6UQVyutxwzNkBhj7wBgejlCCcKeJi Ye+0gDpyFCLKgv/M5w0OUI9VwgTTAgS/SoqNCj/ekZxUimq5NjvhxbO6782SC9Qos2Cz 1/P6wgZwlROgAR/Wfur5g6j2nekdBWwaX5HTo= MIME-Version: 1.0 Received: by 10.102.216.8 with SMTP id o8mr1106889mug.20.1251099070164; Mon, 24 Aug 2009 00:31:10 -0700 (PDT) In-Reply-To: <1250901715.28019.1.camel@ams.xobas.net> References: <1250901715.28019.1.camel@ams.xobas.net> Date: Mon, 24 Aug 2009 09:31:10 +0200 Message-ID: From: Vivien Malerba To: bas.driessen@xobas.com Content-Type: multipart/alternative; boundary=0016364167f9a7f0e60471de3311 Cc: GNOME-DB List Subject: Re: [gnome-db] 4.1.1 release request. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 07:31:27 -0000 --0016364167f9a7f0e60471de3311 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 2009/8/22 Bas Driessen > Hi Vivien, > > There have been many recent changes in libgda master. Is it possible to cut > a 4.1.1 release? > > Thanks, > Bas. > I'll do this ASAP now that I'm back from the hollidays. Vivien --0016364167f9a7f0e60471de3311 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/8/22 Bas Driessen <bas.driessen@xobas.com&g= t;
=20 =20
Hi Vivien,

There have been many recent changes in libgda master. Is it possible to cut= a 4.1.1 release?

Thanks,
Bas.

I'll do this ASAP now that I'm back fro= m the hollidays.

Vivien

--0016364167f9a7f0e60471de3311-- From murrayc@murrayc.com Mon Aug 24 08:13:28 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 40D0C750111 for ; Mon, 24 Aug 2009 08:13:28 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 274 hrs), (distance 15, link: ethernet/modem), [208.97.132.5] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvhHPANPzlVH for ; Mon, 24 Aug 2009 08:13:19 +0000 (GMT) Received: from homiemail-a3.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by menubar.gnome.org (Postfix) with ESMTP id A991F750070 for ; Mon, 24 Aug 2009 08:13:11 +0000 (GMT) Received: from [192.168.24.40] (dslb-084-056-028-053.pools.arcor-ip.net [84.56.28.53]) by homiemail-a3.g.dreamhost.com (Postfix) with ESMTP id B61E9C5AE3; Mon, 24 Aug 2009 01:13:08 -0700 (PDT) From: Murray Cumming To: Vivien Malerba In-Reply-To: References: <1250901715.28019.1.camel@ams.xobas.net> Content-Type: text/plain Date: Mon, 24 Aug 2009 10:13:03 +0200 Message-Id: <1251101583.8748.14.camel@murrayc-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Cc: GNOME-DB List , bas.driessen@xobas.com Subject: Re: [gnome-db] 4.1.1 release request. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 08:13:28 -0000 On Mon, 2009-08-24 at 09:31 +0200, Vivien Malerba wrote: > > > 2009/8/22 Bas Driessen > Hi Vivien, > > There have been many recent changes in libgda master. Is it > possible to cut a 4.1.1 release? > > Thanks, > Bas. > > > I'll do this ASAP now that I'm back from the hollidays. > > Vivien We need a libgda 4.0.x release too, please. And I'm really hoping that a fix for this metastore bug might be in the release: http://bugzilla.gnome.org/show_bug.cgi?id=589822 -- murrayc@murrayc.com www.murrayc.com www.openismus.com From vmalerba@gmail.com Tue Aug 25 07:15:58 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 7ABC47500C2; Tue, 25 Aug 2009 07:15:58 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 2652 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLenlKWIx7RB; Tue, 25 Aug 2009 07:15:49 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id 6CAA2750024; Tue, 25 Aug 2009 07:15:48 +0000 (GMT) Received: by fxm11 with SMTP id 11so2025342fxm.15 for ; Tue, 25 Aug 2009 00:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=n1cWtQA+wvdrei0M9uFc8XSAAHeVr+zzQy2eumxjHqk=; b=K3Iug3397Ycc/4+RnikRFNctyEBAzAkVPdakfuwi2Mh4lSc/6KfPOmwlhXJhZ2vhzf KeKIJNVlcs0j0c2/aeVaG4S1CllIhkPEsJTQQbYWmn4ZGs8Y+ck2CxHaNFsWWAw4Jj0y YBa86x5SlkloI33TR+t72ZTYzrTo/a49xh2A0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=WwG7UFv+XXHVK01jDN5BUS8mEIUJqbx6uGZv9OH8WjAJX39tpJnQCPJtQiIaEqLjNP XFqI0LdlwfWeDtcj9NK+msh3muTY/BfN77sbEF/HWo8IldnO5Y08Ma6xCdWUCwmW20U9 oV4Vqq44P8HP+7paTP/ebNqTa7bpfVq8rDA04= MIME-Version: 1.0 Received: by 10.103.133.25 with SMTP id k25mr2503517mun.62.1251184546266; Tue, 25 Aug 2009 00:15:46 -0700 (PDT) Date: Tue, 25 Aug 2009 09:15:46 +0200 Message-ID: From: Vivien Malerba To: gnome-db list , gnome-announce-list@gnome.org, gnome-office-list@gnome.org Content-Type: multipart/alternative; boundary=0016e65b3ee86dbfd30471f21a18 Subject: [gnome-db] Libgda 4.1.1 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 07:15:58 -0000 --0016e65b3ee86dbfd30471f21a18 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'm pleased to announce version 4.1.1 of Libgda, a development version whic= h will lead to a 4.2 release. Short description: ------------------------ Libgda is a (relatively small) database access library: * a wrapper like ODBC but with more features to access several database engines * a general data model to use CVS or XML files * a meta data extractor (to know all about database objects in a comman way= ) * comes with an SQL console application (like mysql, psql or sqlite3 consoles) * relies on GLib, coded in C, its API is easy to use * optionnally includes some graphical widgets (based on GTK+) for data boun= d representations and some graphical tools Changes from 4.1.0 -------------------------- - it is now possible to use a system installed SQLite, and now uses SQLite 3.6.17 if embedded - new Oracle driver (provider) - improved MySQL and PostgreSQL drivers (providers) - console program improvements - new UI extension based on GTK+ - new program to manage data sources graphically - new program to "browse" a database's schema - improved documentation - better handle SQL identifiers - Lots of corrections and small improvements - Translations: - es (Jorge Gonzalez) - nb (Kjartan Maraas) - sv (Daniel Nylander) - de (Mario Bl=E4ttermann) - it (Marco Ciampa) Notes: -------- * This is unstable development release. While it has had a bit of testing, there are certainly plenty of bugs remaining to be found. This release should not be used in production. * Installing this version will overwrite your existing copy of Libgda 4. If you have problems, you'll need to reinstall it. * Libgda 4.2 will be source and binary compatible with the 4.0 series. * Bugs should be reported to http://bugzilla.gnome.org. See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal information about choosing between Libgda and SQLite when you need a database API. You can find more information at the projects' homepage (http://www.gnome-db.org), or you can ask any question/propose anything you want in the GNOME-DB mailing list, which is available at http://mail.gnome.org/mailman/listinfo/gnome-db-list --0016e65b3ee86dbfd30471f21a18 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'm pleased to announce version 4.1.1 of Libgda, a development version which will lead to a= 4.2 release.

Short description:
------------------------
Libgda is a (relatively small) database access library:
* a wrapper like ODBC but with more features to access several database eng= ines
* a general data model to use CVS or XML files
* a meta data extractor (= to know all about database objects in a comman way)
* comes with an SQL = console application (like mysql, psql or sqlite3 consoles)
* relies on G= Lib, coded in C, its API is easy to use
* optionnally includes some graphical widgets (based on GTK+) for data boun= d representations
=A0 and some graphical tools

Changes from 4.1.0
--------------------------
=A0- it is now possible to use a system installed SQLite, and now uses
= =A0=A0 SQLite 3.6.17 if embedded
=A0- new Oracle driver (provider)
= =A0- improved MySQL and PostgreSQL drivers (providers)
=A0- console prog= ram improvements
=A0- new UI extension based on GTK+
=A0- new program to manage data sour= ces graphically
=A0- new program to "browse" a database's = schema
=A0- improved documentation
=A0- better handle SQL identifiers=
=A0- Lots of corrections and small improvements
=A0- Translations:
=A0=A0=A0=A0=A0=A0=A0 - es (Jorge Gonzalez)
=A0=A0= =A0=A0=A0=A0=A0 - nb (Kjartan Maraas)
=A0=A0=A0=A0=A0=A0=A0 - sv (Daniel= Nylander)
=A0=A0=A0=A0=A0=A0=A0 - de (Mario Bl=E4ttermann)
=A0=A0=A0= =A0=A0=A0=A0 - it (Marco Ciampa)

Notes:
--------
* This is unstable development release. While it has= had
a bit of testing, there are certainly plenty of bugs
remaini= ng to be found. This release should not be used
in production.

* Installing this version will overwrite your existing
copy of Li= bgda 4. If you have problems, you'll need to
reinstall it.

= * Libgda 4.2 will be source and binary compatible with
the 4.0 series= .

* Bugs should be reported to http://bugzilla.gnome.org.
See the http://live.gnome.org/ChooseLibgd= aSQLite page f= or additionnal information about choosing
between Libgda and= SQLite when you need a database API.

You can find more information at the projects' homepage
(http://www.gnome-db= .org), or you can ask any question/propose
anything you want in the GNOME-DB mailing list, which is available at
http://mail.gnome.org/mailman/listinfo/gnome-db-list
--0016e65b3ee86dbfd30471f21a18-- From vmalerba@gmail.com Tue Aug 25 07:22:56 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 359A27500B0; Tue, 25 Aug 2009 07:22:56 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 2655 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wErHLhcZKg8y; Tue, 25 Aug 2009 07:22:46 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id 3A94D750260; Tue, 25 Aug 2009 07:22:36 +0000 (GMT) Received: by fxm11 with SMTP id 11so2027936fxm.15 for ; Tue, 25 Aug 2009 00:22:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=o0HnE7iiUCzzQgEQtnw5rOgEFVM3Gog8m7xmU467F4E=; b=e85U6AmPPagRcuR6T9cHWpnPXqYc83z30aalq8vThZxu9INEBxCkllvRbzB3SmegEZ JmHgHEggwvr3QIu5cmY1RVLGjFumFxm2MD3CvBG7Rle5gM5wzb9YCmOqImYVoG8n+pu8 W+KqO3+RYc52HCy4XDnf/SJcMRbpzK58yF6hA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=wCgVo7drPwnXdB4uAqH85tm5xtK1f5HP2GNqZx2TPzbFfASZJgMuA0wbV1mrrug8Pn BFAL5mNe/Qr3P2MJboQ2YGoAAFB82hdK/FZ0/eZ5lxlNeU65zfbeF09yDgetdE2s2AlS 5uhy8+ekOivDHjeGVTK3gknOR64UPaQ2Xv8WQ= MIME-Version: 1.0 Received: by 10.103.122.22 with SMTP id z22mr2372732mum.123.1251184954494; Tue, 25 Aug 2009 00:22:34 -0700 (PDT) Date: Tue, 25 Aug 2009 09:22:33 +0200 Message-ID: From: Vivien Malerba To: gnome-db list , gnome-announce-list@gnome.org, gnome-office-list@gnome.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [gnome-db] Libgda 4.0.3 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 07:22:56 -0000 I'm pleased to announce version 4.0.3 of Libgda, which is a maintenance release of the 4.0 serie. Short description: ------------------------ Libgda is a (relatively small) database access library: * a wrapper like ODBC but with more features to access several database engines * a general data model to use CVS or XML files * a meta data extractor (to know all about database objects in a comman way) * comes with an SQL console application (like mysql, psql or sqlite3 consoles) * relies on GLib, coded in C, its API is easy to use Changes from 4.0.2 --------------------------- - improved MySQL and PostgreSQL drivers (providers) - console program improvements - improved documentation - better handle SQL identifiers - Lots of corrections and small improvements Tarballs are available at http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0 Pease note that Win32 archives are also available at http://ftp.gnome.org/pub/GNOME/binaries/win32/ See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal information about choosing between Libgda and SQLite when you need a database API. You can find more information at the projects' homepage (http://www.gnome-db.org), or you can ask any question/propose anything you want in the GNOME-DB mailing list, which is available at http://mail.gnome.org/mailman/listinfo/gnome-db-list From vmalerba@gmail.com Tue Aug 25 17:33:36 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id D733A7502DC for ; Tue, 25 Aug 2009 17:33:36 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (firewall!) (up: 3216 hrs), (distance 17, link: (Google 2)), [74.125.78.25] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOgi8aVicfbh for ; Tue, 25 Aug 2009 17:33:30 +0000 (GMT) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by menubar.gnome.org (Postfix) with ESMTP id EAABC7502B0 for ; Tue, 25 Aug 2009 17:33:21 +0000 (GMT) Received: by ey-out-2122.google.com with SMTP id 22so754929eye.49 for ; Tue, 25 Aug 2009 10:33:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=s08cquHlM1Yr2qUzBEMl4GbWMnwGP1Wby9vpY05pqmg=; b=SfMbYufVEGM6vLhk0O/6S6y8Hapayzeh2dpWMIExfV8cmsxIbyZV5HOVvtLqkXDN42 TiHj9vLVvutCt9MESL2LSv9SuDCSRVuVx4q4/dT7skuJBl7MdpFSG0dqCC2oYqNco24E My4I8k08vhziTF3mkoHybXQm5M+rSWuHxMUcc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tT6JY0FXr/T7CHxsfb13DwZLw10zf5jWmzj7xGvfjNRAZLgNUOKUZx1Lv30vaJs0qZ iLRo10Plr7leKxm8cHVqkhz2r83Lxlbn5s+p9JNNyr0T95jKUIs1pfTdqvTaMLAX5/HZ t6an6kmvEjdUu3PuHpxx/Crq6FarBltdAr2YY= MIME-Version: 1.0 Received: by 10.103.76.32 with SMTP id d32mr2837343mul.98.1251221599430; Tue, 25 Aug 2009 10:33:19 -0700 (PDT) In-Reply-To: <1250249831.17353.12.camel@ams.xobas.net> References: <1250249831.17353.12.camel@ams.xobas.net> Date: Tue, 25 Aug 2009 19:33:19 +0200 Message-ID: From: Vivien Malerba To: bas.driessen@xobas.com Content-Type: multipart/alternative; boundary=0016e65b61ccf828d40471faba1c Cc: GNOME-DB List Subject: Re: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 17:33:37 -0000 --0016e65b61ccf828d40471faba1c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 2009/8/14 Bas Driessen > Hi Vivien, > > You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. > There is a problem with this that if set and a partial meta store update is > performed, the meta store is not updated. If using any of the other > GDA_CONNECTION_OPTIONS all works fine. > > I have attached 2 small c programs to re-produce this issue. The database > provider is MySQL, my (test) database is called 'stock' and the DSN is > 'mystock' > > -1 rm /tmp/mysql_meta.db > -2 in MySQL: drop table xPartsUC; > -3 Run mysql_full (source attached) > -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, > Description varchar(30)); > -5 Run mysql_partial (source attached) > -6 sqlite3 /tmp/mysql_meta.db then run: select * from _tables where > table_name = '"xPartsUC"'; > -7 nothing there. Run mysql_full and the entry is there. > The cause of this problem was that I had forgotten to implement a virtual method. This should now be fixed in the master branch, can you check? > > > On a side note, how do I pass 2 or more GDA_CONNECTION_OPTIONS to > gda_connection_open_from_dsn() ? > > ie, if I want to set GDA_CONNECTION_OPTIONS_THREAD_SAFE and the > GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE option? > simply use the logical OR operator: ..., GDA_CONNECTION_OPTIONS_THREAD_SAFE | GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE,... Regards, Vivien --0016e65b61ccf828d40471faba1c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

2009/8/14 Bas Driessen <bas.driessen@xobas.com&g= t;
=20 =20
Hi Vivien,

You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. Ther= e is a problem with this that if set and a partial meta store update is per= formed, the meta store is not updated. If using any of the other GDA_CONNEC= TION_OPTIONS all works fine.

I have attached 2 small c programs to re-produce this issue. The database p= rovider is MySQL, my (test) database is called=A0 'stock' and the D= SN is 'mystock'

-1 rm /tmp/mysql_meta.db
-2 in MySQL: drop table xPartsUC;
-3 Run mysql_full (source attached)
-4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, Descrip= tion varchar(30));
-5 Run mysql_partial (source attached)
-6 sqlite3 /tmp/mysql_meta.db=A0 then run: select * from _tables where tabl= e_name =3D '"xPartsUC"';
-7 nothing there. Run mysql_full and the entry is there.
=

The cause of this problem was that I had forgotten to implement a = virtual method. This should now be fixed in the master branch, can you chec= k?


On a side note, how do I pass 2 or more GDA_CONNECTION_OPTIONS to gda_conne= ction_open_from_dsn() ?

ie, if I want to set GDA_CONNECTION_OPTIONS_THREAD_SAFE and the GDA_CONNECT= ION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE option?
<= br>simply use the logical OR operator:
..., GDA_CONNECTION_OPTIONS_THREA= D_SAFE | GDA_CONNECTION_OPTIONS_SQL_IDENTIFIERS_CASE_SENSITIVE,...


Regards,

Vivien


--0016e65b61ccf828d40471faba1c-- From bas.driessen@xobas.com Wed Aug 26 08:21:19 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 2B14C75000B for ; Wed, 26 Aug 2009 08:21:19 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 1393 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXJsO7b0M0UL for ; Wed, 26 Aug 2009 08:21:12 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 64BD3750007 for ; Wed, 26 Aug 2009 08:21:03 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n7Q8KtmA004328 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Aug 2009 04:20:58 -0400 From: Bas Driessen To: Vivien Malerba In-Reply-To: References: <1250249831.17353.12.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-jBYBSglTpckN08VQWFiI" Organization: Xobas Software Date: Wed, 26 Aug 2009 18:20:54 +1000 Message-Id: <1251274854.20200.27.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9741/Wed Aug 26 01:15:49 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 08:21:19 -0000 --=-jBYBSglTpckN08VQWFiI Content-Type: text/plain Content-Transfer-Encoding: 7bit On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote: > > > > 2009/8/14 Bas Driessen > > Hi Vivien, > > You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE > option. There is a problem with this that if set and a partial > meta store update is performed, the meta store is not updated. > If using any of the other GDA_CONNECTION_OPTIONS all works > fine. > > I have attached 2 small c programs to re-produce this issue. > The database provider is MySQL, my (test) database is called > 'stock' and the DSN is 'mystock' > > -1 rm /tmp/mysql_meta.db > -2 in MySQL: drop table xPartsUC; > -3 Run mysql_full (source attached) > -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY > KEY, Description varchar(30)); > -5 Run mysql_partial (source attached) > -6 sqlite3 /tmp/mysql_meta.db then run: select * from _tables > where table_name = '"xPartsUC"'; > -7 nothing there. Run mysql_full and the entry is there. > > The cause of this problem was that I had forgotten to implement a > virtual method. This should now be fixed in the master branch, can you > check? > Initial testing shows that this is working OK now. Will hit it a bit harder over the next couple of days, but it looks like this bug is fixed. Thanks for that Vivien! Bas. --=-jBYBSglTpckN08VQWFiI Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote:


2009/8/14 Bas Driessen <bas.driessen@xobas.com>
Hi Vivien,

You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There is a problem with this that if set and a partial meta store update is performed, the meta store is not updated. If using any of the other GDA_CONNECTION_OPTIONS all works fine.

I have attached 2 small c programs to re-produce this issue. The database provider is MySQL, my (test) database is called  'stock' and the DSN is 'mystock'

-1 rm /tmp/mysql_meta.db
-2 in MySQL: drop table xPartsUC;
-3 Run mysql_full (source attached)
-4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, Description varchar(30));
-5 Run mysql_partial (source attached)
-6 sqlite3 /tmp/mysql_meta.db  then run: select * from _tables where table_name = '"xPartsUC"';
-7 nothing there. Run mysql_full and the entry is there.

The cause of this problem was that I had forgotten to implement a virtual method. This should now be fixed in the master branch, can you check?


Initial testing shows that this is working OK now. Will hit it a bit harder over the next couple of days, but it looks like this bug is fixed.

Thanks for that Vivien!

Bas.

--=-jBYBSglTpckN08VQWFiI-- From vmalerba@gmail.com Wed Aug 26 08:27:12 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 49250750007 for ; Wed, 26 Aug 2009 08:27:12 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 2905 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anSsA5bQYg+1 for ; Wed, 26 Aug 2009 08:27:04 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id AC5D4750004 for ; Wed, 26 Aug 2009 08:26:55 +0000 (GMT) Received: by fxm11 with SMTP id 11so2844940fxm.15 for ; Wed, 26 Aug 2009 01:26:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cDAeYSs8jtOJ1KQmOHZii7OVBDzl3EzMj5+LDoqaySY=; b=ZZ7zvCu1dp4g0w1Jp1lI7zx4LiVTPBDJ59bcrqPzybaYM8LklcINxZGto9466pBqdI 1oBLzwtrlspmwZ2BsYFq6LWTME64z2Kd74q45Aadcr7JRbr6DgFnx/3CH7/vaaO5b5Ry 2fYGm0UE1SqDKHFCZ4Vuxuu/skYKDcLsPd+Oo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sOMpvvzi34JXEHWjI4AGUhmw9w3/g+XBjq2+Lq1QmvbJV7fION8iOp9RgZbD03IyQ+ 8nF7F92i5SAJzDk+ivoOOSmoiNVeBayeBkFVEEeefEbKBVDN2SyV6L/DO4Uby5zWkVxC Gk7QCUJC4szITolqk558eu6sF6OWLAsclVklc= MIME-Version: 1.0 Received: by 10.102.216.8 with SMTP id o8mr2733751mug.20.1251275212928; Wed, 26 Aug 2009 01:26:52 -0700 (PDT) In-Reply-To: <1251274854.20200.27.camel@ams.xobas.net> References: <1250249831.17353.12.camel@ams.xobas.net> <1251274854.20200.27.camel@ams.xobas.net> Date: Wed, 26 Aug 2009 10:26:52 +0200 Message-ID: From: Vivien Malerba To: bas.driessen@xobas.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: GNOME-DB List Subject: Re: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.10 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 08:27:12 -0000 2009/8/26 Bas Driessen : > On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote: > > > 2009/8/14 Bas Driessen > > Hi Vivien, > > You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There > is a problem with this that if set and a partial meta store update is > performed, the meta store is not updated. If using any of the other > GDA_CONNECTION_OPTIONS all works fine. > > I have attached 2 small c programs to re-produce this issue. The database > provider is MySQL, my (test) database is called 'stock' and the DSN is > 'mystock' > > -1 rm /tmp/mysql_meta.db > -2 in MySQL: drop table xPartsUC; > -3 Run mysql_full (source attached) > -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, > Description varchar(30)); > -5 Run mysql_partial (source attached) > -6 sqlite3 /tmp/mysql_meta.db then run: select * from _tables where > table_name = '"xPartsUC"'; > -7 nothing there. Run mysql_full and the entry is there. > > The cause of this problem was that I had forgotten to implement a virtual > method. This should now be fixed in the master branch, can you check? > > > Initial testing shows that this is working OK now. Will hit it a bit harder > over the next couple of days, but it looks like this bug is fixed. > Ok, great. BTW, next time you find a bug it'd be better if you could file a bug report in bugzilla at http://bugzilla.gnome.org/, as it's then easier to follow its correction and keep an history than in a mail. Regards, Vivien From bas.driessen@xobas.com Wed Aug 26 09:08:32 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 7D22E7501A7 for ; Wed, 26 Aug 2009 09:08:32 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 1395 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9osWCjsbGR8F for ; Wed, 26 Aug 2009 09:08:24 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 100877500C5 for ; Wed, 26 Aug 2009 09:08:15 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n7Q988kG004856 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Aug 2009 05:08:10 -0400 From: Bas Driessen To: Vivien Malerba In-Reply-To: References: <1250249831.17353.12.camel@ams.xobas.net> <1251274854.20200.27.camel@ams.xobas.net> Content-Type: multipart/alternative; boundary="=-mE17Ov0Zl9bGTWhztF/7" Organization: Xobas Software Date: Wed, 26 Aug 2009 19:08:07 +1000 Message-Id: <1251277687.20200.30.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9741/Wed Aug 26 01:15:49 2009 on fra.xobas.net X-Virus-Status: Clean Cc: GNOME-DB List Subject: Re: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue. X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 09:08:32 -0000 --=-mE17Ov0Zl9bGTWhztF/7 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Wed, 2009-08-26 at 10:26 +0200, Vivien Malerba wrote: > 2009/8/26 Bas Driessen : > > On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote: > > > > > > 2009/8/14 Bas Driessen > > > > Hi Vivien, > > > > You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There > > is a problem with this that if set and a partial meta store update is > > performed, the meta store is not updated. If using any of the other > > GDA_CONNECTION_OPTIONS all works fine. > > > > I have attached 2 small c programs to re-produce this issue. The database > > provider is MySQL, my (test) database is called 'stock' and the DSN is > > 'mystock' > > > > -1 rm /tmp/mysql_meta.db > > -2 in MySQL: drop table xPartsUC; > > -3 Run mysql_full (source attached) > > -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY, > > Description varchar(30)); > > -5 Run mysql_partial (source attached) > > -6 sqlite3 /tmp/mysql_meta.db then run: select * from _tables where > > table_name = '"xPartsUC"'; > > -7 nothing there. Run mysql_full and the entry is there. > > > > The cause of this problem was that I had forgotten to implement a virtual > > method. This should now be fixed in the master branch, can you check? > > > > > > Initial testing shows that this is working OK now. Will hit it a bit harder > > over the next couple of days, but it looks like this bug is fixed. > > > > Ok, great. > > BTW, next time you find a bug it'd be better if you could file a bug > report in bugzilla at http://bugzilla.gnome.org/, as it's then easier > to follow its correction and keep an history than in a mail. No problem Vivien. Was not sure if bugs in bugzilla were actually followed up, therefore the mailing list requests. Will channel them through bugzilla in the future as requested. Bas. --=-mE17Ov0Zl9bGTWhztF/7 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit On Wed, 2009-08-26 at 10:26 +0200, Vivien Malerba wrote:
2009/8/26 Bas Driessen <bas.driessen@xobas.com>:
> On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote:
>
>
> 2009/8/14 Bas Driessen <bas.driessen@xobas.com>
>
> Hi Vivien,
>
> You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There
> is a problem with this that if set and a partial meta store update is
> performed, the meta store is not updated. If using any of the other
> GDA_CONNECTION_OPTIONS all works fine.
>
> I have attached 2 small c programs to re-produce this issue. The database
> provider is MySQL, my (test) database is called  'stock' and the DSN is
> 'mystock'
>
> -1 rm /tmp/mysql_meta.db
> -2 in MySQL: drop table xPartsUC;
> -3 Run mysql_full (source attached)
> -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY,
> Description varchar(30));
> -5 Run mysql_partial (source attached)
> -6 sqlite3 /tmp/mysql_meta.db  then run: select * from _tables where
> table_name = '"xPartsUC"';
> -7 nothing there. Run mysql_full and the entry is there.
>
> The cause of this problem was that I had forgotten to implement a virtual
> method. This should now be fixed in the master branch, can you check?
>
>
> Initial testing shows that this is working OK now. Will hit it a bit harder
> over the next couple of days, but it looks like this bug is fixed.
>

Ok, great.

BTW, next time you find a bug it'd be better if you could file a bug
report in bugzilla at http://bugzilla.gnome.org/, as it's then easier
to follow its correction and keep an history than in a mail.

No problem Vivien. Was not sure if bugs in bugzilla were actually followed up, therefore the mailing list requests. Will channel them through bugzilla in the future as requested.

Bas. --=-mE17Ov0Zl9bGTWhztF/7-- From murrayc@murrayc.com Wed Aug 26 14:41:05 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 9B2E975017A for ; Wed, 26 Aug 2009 14:41:05 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 3) (up: 649 hrs), (distance 15, link: ethernet/modem), [208.97.132.202] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zEUReNMfUMI4 for ; Wed, 26 Aug 2009 14:40:55 +0000 (GMT) Received: from homiemail-a14.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by menubar.gnome.org (Postfix) with ESMTP id 976D8750222 for ; Wed, 26 Aug 2009 14:40:47 +0000 (GMT) Received: from [192.168.24.48] (dslb-084-056-012-117.pools.arcor-ip.net [84.56.12.117]) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPA id 2EFA18C061; Wed, 26 Aug 2009 07:40:44 -0700 (PDT) From: Murray Cumming To: Vivien Malerba In-Reply-To: References: Content-Type: text/plain Date: Wed, 26 Aug 2009 16:40:42 +0200 Message-Id: <1251297642.3604.34.camel@murrayc-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Cc: gnome-db list Subject: Re: [gnome-db] Libgda 4.0.3 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 14:41:05 -0000 Now that all the major metastore issues are fixed as far as Glom is concerned, thanks to you, it would be really nice to have another release so I can do a Glom release, please. On Tue, 2009-08-25 at 09:22 +0200, Vivien Malerba wrote: > I'm pleased to announce version 4.0.3 of Libgda, which is a > maintenance release of the 4.0 serie. > > Short description: > ------------------------ > Libgda is a (relatively small) database access library: > * a wrapper like ODBC but with more features to access several database engines > * a general data model to use CVS or XML files > * a meta data extractor (to know all about database objects in a comman way) > * comes with an SQL console application (like mysql, psql or sqlite3 consoles) > * relies on GLib, coded in C, its API is easy to use > > Changes from 4.0.2 > --------------------------- > - improved MySQL and PostgreSQL drivers (providers) > - console program improvements > - improved documentation > - better handle SQL identifiers > - Lots of corrections and small improvements > > Tarballs are available at http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0 > Pease note that Win32 archives are also available at > http://ftp.gnome.org/pub/GNOME/binaries/win32/ > > > See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal > information about choosing > between Libgda and SQLite when you need a database API. > > You can find more information at the projects' homepage > (http://www.gnome-db.org), or you can ask any question/propose > anything you want in the GNOME-DB mailing list, which is available at > http://mail.gnome.org/mailman/listinfo/gnome-db-list > _______________________________________________ > gnome-db-list mailing list > gnome-db-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-db-list -- murrayc@murrayc.com www.murrayc.com www.openismus.com From azagli@libero.it Wed Aug 26 16:29:08 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id D8335750081 for ; Wed, 26 Aug 2009 16:29:08 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 3) (NAT!) (up: 4697 hrs), (distance 23, link: GPRS, T1, FreeS/WAN), [212.52.84.107] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOI8vtYCxuUG for ; Wed, 26 Aug 2009 16:29:03 +0000 (GMT) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by menubar.gnome.org (Postfix) with ESMTP id 84E2075002E for ; Wed, 26 Aug 2009 16:28:54 +0000 (GMT) Received: from phobos.saetta.homelinux.org (151.49.31.236) by cp-out7.libero.it (8.5.107) id 4A700F4301CEA8ED for gnome-db-list@gnome.org; Wed, 26 Aug 2009 18:28:52 +0200 Received: from localhost (localhost [127.0.0.1]) by phobos.saetta.homelinux.org (Postfix) with ESMTP id D74699FC1 for ; Wed, 26 Aug 2009 18:08:38 +0200 (CEST) Received: from 10.0.0.2 ([10.0.0.2]) by 10.0.0.4 (Horde Framework) with HTTP; Wed, 26 Aug 2009 18:08:37 +0200 Message-ID: <20090826180837.55196wbizbvtah34@10.0.0.4> Date: Wed, 26 Aug 2009 18:08:37 +0200 From: Andrea Zagli To: gnome-db-list@gnome.org References: <20090810185858.16876cjiiloozchs@10.0.0.4> <20090812092744.20021qc4rqqr5on4@saetta.homelinux.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3.2) Subject: Re: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 16:29:09 -0000 Il giorno mer 12 ago 2009 15:10:00 CEST, Vivien Malerba ha scritto: > [...] > Yes, the same applies. The correction was made in both the 4.0 and 4.1 > (master) branches. i just tried 4.1.1 and select distinct year from customer now works, but select * from customers where exists (select orders.* from orders =20 where customers.id =3D orders.id_customers) return the same error =C2=ABnear "(": syntax error=C2=BB From vmalerba@gmail.com Wed Aug 26 19:37:57 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id BEC5B750077 for ; Wed, 26 Aug 2009 19:37:57 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=2 tests=[BAYES_00=-2.599] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 3017 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WUwYievLzZbj for ; Wed, 26 Aug 2009 19:37:51 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id 36464750081 for ; Wed, 26 Aug 2009 19:37:42 +0000 (GMT) Received: by fxm11 with SMTP id 11so395426fxm.15 for ; Wed, 26 Aug 2009 12:37:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nmKzOKjtrMH010Umuk17JsCSFyFUTEnlSIKShCLXiF8=; b=UmpMnbIfwoilk/CLKZ9uZnVv1PAm1FNkhVGOdy9l1nsODDo7qa2Sv1jKAhAfIzd187 wJxavZBoGQ8CpXQX8et0fXU0/CHV4ifsnA9C2DjVuMDkvAmtktbfLKR/JhwUWgmo+6kv nTM2KgErecDE5+WwWN5ROzeCjyQkG5utw2A9A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=J/DY4vCu0ieqeOJb2FQykqlsCWUkMH1wtUibhB9/h1GPVVoxKq+gJpa+076DNJT1qu KpoMYAxzgp9u9/Hl/aKrNHJ238tyjCqzLvbAKOJuI4RrLSv4Xdoq1rVlmt/uIUi7O4AD T+b6C90TRMdmttF7oDsSg/4bw1+AcU1JiHzLc= MIME-Version: 1.0 Received: by 10.103.125.19 with SMTP id c19mr3800654mun.59.1251315460169; Wed, 26 Aug 2009 12:37:40 -0700 (PDT) In-Reply-To: <20090826180837.55196wbizbvtah34@10.0.0.4> References: <20090810185858.16876cjiiloozchs@10.0.0.4> <20090812092744.20021qc4rqqr5on4@saetta.homelinux.org> <20090826180837.55196wbizbvtah34@10.0.0.4> Date: Wed, 26 Aug 2009 21:37:40 +0200 Message-ID: From: Vivien Malerba To: Andrea Zagli Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: gnome-db-list@gnome.org Subject: Re: [gnome-db] strange sql parsing behavior X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 19:37:58 -0000 2009/8/26 Andrea Zagli : > Il giorno mer 12 ago 2009 15:10:00 CEST, Vivien Malerba ha scritto: >> >> [...] >> Yes, the same applies. The correction was made in both the 4.0 and 4.1 >> (master) branches. > > i just tried 4.1.1 and > > select distinct year from customer > > now works, but > > select * from customers where exists (select orders.* from orders where > customers.id =3D orders.id_customers) > > return the same error =ABnear "(": syntax error=BB Ok, this was another rendering problem bug: the statement was rendered as: select * from customers where exists ((select orders.* from orders where customers.id =3D orders.id_customers)) which SQLite does not like. Can you check with git master? Thanks, Vivien From bas.driessen@xobas.com Wed Aug 26 23:07:10 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 3469375002E for ; Wed, 26 Aug 2009 23:07:10 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.521 X-Spam-Level: X-Spam-Status: No, score=-2.521 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 1430 hrs), (distance 15, link: ethernet/modem), [208.78.101.125] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uz5biXzn3-ug for ; Wed, 26 Aug 2009 23:07:01 +0000 (GMT) Received: from fra.xobas.net (fra.xobas.net [208.78.101.125]) by menubar.gnome.org (Postfix) with ESMTP id 3E23C750085 for ; Wed, 26 Aug 2009 23:06:52 +0000 (GMT) Received: from [192.168.1.14] (ppp214-42.static.internode.on.net [59.167.214.42]) (authenticated bits=0) by fra.xobas.net (8.14.3/8.14.3) with ESMTP id n7QN6bVL014659 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 26 Aug 2009 19:06:46 -0400 From: Bas Driessen To: Murray Cumming In-Reply-To: <1251297642.3604.34.camel@murrayc-desktop> References: <1251297642.3604.34.camel@murrayc-desktop> Content-Type: multipart/alternative; boundary="=-+KQqdc1RSJ8CfPCNwiWM" Organization: Xobas Software Date: Thu, 27 Aug 2009 09:06:36 +1000 Message-Id: <1251327996.19601.3.camel@ams.xobas.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) X-Virus-Scanned: ClamAV 0.94.2/9744/Wed Aug 26 13:52:36 2009 on fra.xobas.net X-Virus-Status: Clean Cc: gnome-db list , Vivien Malerba Subject: Re: [gnome-db] Libgda 4.0.3 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: bas.driessen@xobas.com List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2009 23:07:10 -0000 --=-+KQqdc1RSJ8CfPCNwiWM Content-Type: text/plain Content-Transfer-Encoding: 7bit + 1. I know the release is only 2 days old, but this critical metabug (that was fixed just after the release) really does not make things work for MySQL. Thanks, Bas. On Wed, 2009-08-26 at 16:40 +0200, Murray Cumming wrote: > Now that all the major metastore issues are fixed as far as Glom is > concerned, thanks to you, it would be really nice to have another > release so I can do a Glom release, please. > > On Tue, 2009-08-25 at 09:22 +0200, Vivien Malerba wrote: > > I'm pleased to announce version 4.0.3 of Libgda, which is a > > maintenance release of the 4.0 serie. > > > > Short description: > > ------------------------ > > Libgda is a (relatively small) database access library: > > * a wrapper like ODBC but with more features to access several database engines > > * a general data model to use CVS or XML files > > * a meta data extractor (to know all about database objects in a comman way) > > * comes with an SQL console application (like mysql, psql or sqlite3 consoles) > > * relies on GLib, coded in C, its API is easy to use > > > > Changes from 4.0.2 > > --------------------------- > > - improved MySQL and PostgreSQL drivers (providers) > > - console program improvements > > - improved documentation > > - better handle SQL identifiers > > - Lots of corrections and small improvements > > > > Tarballs are available at http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0 > > Pease note that Win32 archives are also available at > > http://ftp.gnome.org/pub/GNOME/binaries/win32/ > > > > > > See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal > > information about choosing > > between Libgda and SQLite when you need a database API. > > > > You can find more information at the projects' homepage > > (http://www.gnome-db.org), or you can ask any question/propose > > anything you want in the GNOME-DB mailing list, which is available at > > http://mail.gnome.org/mailman/listinfo/gnome-db-list > > _______________________________________________ > > gnome-db-list mailing list > > gnome-db-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-db-list --=-+KQqdc1RSJ8CfPCNwiWM Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit + 1.

I know the release is only 2 days old, but this critical metabug (that was fixed just after the release) really does not make things work for MySQL.

Thanks,
Bas.


On Wed, 2009-08-26 at 16:40 +0200, Murray Cumming wrote:
Now that all the major metastore issues are fixed as far as Glom is
concerned, thanks to you, it would be really nice to have another
release so I can do a Glom release, please.

On Tue, 2009-08-25 at 09:22 +0200, Vivien Malerba wrote:
> I'm pleased to announce version 4.0.3 of Libgda, which is a
> maintenance release of the 4.0 serie.
> 
> Short description:
> ------------------------
> Libgda is a (relatively small) database access library:
> * a wrapper like ODBC but with more features to access several database engines
> * a general data model to use CVS or XML files
> * a meta data extractor (to know all about database objects in a comman way)
> * comes with an SQL console application (like mysql, psql or sqlite3 consoles)
> * relies on GLib, coded in C, its API is easy to use
> 
> Changes from 4.0.2
> ---------------------------
>  - improved MySQL and PostgreSQL drivers (providers)
>  - console program improvements
>  - improved documentation
>  - better handle SQL identifiers
>  - Lots of corrections and small improvements
> 
> Tarballs are available at http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0
> Pease note that Win32 archives are also available at
> http://ftp.gnome.org/pub/GNOME/binaries/win32/
> 
> 
> See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal
> information about choosing
> between Libgda and SQLite when you need a database API.
> 
> You can find more information at the projects' homepage
> (http://www.gnome-db.org), or you can ask any question/propose
> anything you want in the GNOME-DB mailing list, which is available at
> http://mail.gnome.org/mailman/listinfo/gnome-db-list
> _______________________________________________
> gnome-db-list mailing list
> gnome-db-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-db-list
--=-+KQqdc1RSJ8CfPCNwiWM-- From vmalerba@gmail.com Thu Aug 27 06:02:39 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 98B0E750092 for ; Thu, 27 Aug 2009 06:02:39 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 11508 hrs), (distance 16, link: ethernet/modem), [209.85.219.210] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Z+CNtN-7oyT for ; Thu, 27 Aug 2009 06:02:30 +0000 (GMT) Received: from mail-ew0-f210.google.com (mail-ew0-f210.google.com [209.85.219.210]) by menubar.gnome.org (Postfix) with ESMTP id 7722A7500AE for ; Thu, 27 Aug 2009 06:02:22 +0000 (GMT) Received: by ewy6 with SMTP id 6so910479ewy.34 for ; Wed, 26 Aug 2009 23:02:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5JHAgLXf9BMIi+v8RIN5j8dKxJlXIg2CvyQor5A6wYk=; b=rhA+H3Gky7O43YUedQKY/Wuyd+rADU83mbT1nqT5Y//mePRaUHp+lorR9VHf5xJhNb IBq4IJk7TvNB5K4S19OfKMdBzng+wqqdGHTvWlwovjcLmSjPOEh0BK5XcahJKjyGAYBM 0JXNKpDMRtntZWKbyFhvCCekj/IaRX5Fcxe/Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xyNHA815fG1OAkwImlBGFXitlo7VAsUqfrb8NQdLxLjuMPiwzSBh7XRTTzs2bO/YnO 2y8DfEEXTeqR0PvqhTuKiaw7F+GPUW2zKqGJmwhljiQwqWNTyQ4fEJC9O6c5yhccGStQ 1T0i1WJWUPHGTvXBuTqtaOEs8maeUkHHAkOsI= MIME-Version: 1.0 Received: by 10.103.37.34 with SMTP id p34mr4160600muj.84.1251352940172; Wed, 26 Aug 2009 23:02:20 -0700 (PDT) In-Reply-To: <1251327996.19601.3.camel@ams.xobas.net> References: <1251297642.3604.34.camel@murrayc-desktop> <1251327996.19601.3.camel@ams.xobas.net> Date: Thu, 27 Aug 2009 08:02:20 +0200 Message-ID: From: Vivien Malerba To: bas.driessen@xobas.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: gnome-db list , Murray Cumming Subject: Re: [gnome-db] Libgda 4.0.3 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Aug 2009 06:02:39 -0000 Ok, will do a 4.0.4 ASAP. Vivien 2009/8/27 Bas Driessen : > + 1. > > I know the release is only 2 days old, but this critical metabug (that was > fixed just after the release) really does not make things work for MySQL. > > Thanks, > Bas. > > > On Wed, 2009-08-26 at 16:40 +0200, Murray Cumming wrote: > > Now that all the major metastore issues are fixed as far as Glom is > concerned, thanks to you, it would be really nice to have another > release so I can do a Glom release, please. > > On Tue, 2009-08-25 at 09:22 +0200, Vivien Malerba wrote: >> I'm pleased to announce version 4.0.3 of Libgda, which is a >> maintenance release of the 4.0 serie. >> >> Short description: >> ------------------------ >> Libgda is a (relatively small) database access library: >> * a wrapper like ODBC but with more features to access several database >> engines >> * a general data model to use CVS or XML files >> * a meta data extractor (to know all about database objects in a comman >> way) >> * comes with an SQL console application (like mysql, psql or sqlite3 >> consoles) >> * relies on GLib, coded in C, its API is easy to use >> >> Changes from 4.0.2 >> --------------------------- >> - improved MySQL and PostgreSQL drivers (providers) >> - console program improvements >> - improved documentation >> - better handle SQL identifiers >> - Lots of corrections and small improvements >> >> Tarballs are available at >> http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0 >> Pease note that Win32 archives are also available at >> http://ftp.gnome.org/pub/GNOME/binaries/win32/ >> >> >> See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal >> information about choosing >> between Libgda and SQLite when you need a database API. >> >> You can find more information at the projects' homepage >> (http://www.gnome-db.org), or you can ask any question/propose >> anything you want in the GNOME-DB mailing list, which is available at >> http://mail.gnome.org/mailman/listinfo/gnome-db-list >> _______________________________________________ >> gnome-db-list mailing list >> gnome-db-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-db-list > From vmalerba@gmail.com Mon Aug 31 06:17:45 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id B64C875000A; Mon, 31 Aug 2009 06:17:45 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 3988 hrs), (distance 15, link: ethernet/modem), [209.85.218.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8XIGWoBIQMQ; Mon, 31 Aug 2009 06:17:37 +0000 (GMT) Received: from mail-bw0-f215.google.com (mail-bw0-f215.google.com [209.85.218.215]) by menubar.gnome.org (Postfix) with ESMTP id 2D8BC75008E; Mon, 31 Aug 2009 06:17:27 +0000 (GMT) Received: by bwz11 with SMTP id 11so2574471bwz.15 for ; Sun, 30 Aug 2009 23:17:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Dm28wxp9KxdlvD8ZkxRSTOockfiLQDpNBrmWiGykotc=; b=GEWAcSdwUgODaPujlgR28xiHYJ1HVdC3TLqVuDXv2AxGCZWgnK7DNE/tyNwz1WRFpO 6ATjxKspMpckF0wu+SbV/o4TAfyQpj/8l83JbckkYGDBBl6NAAEFepQNvyrnOK3oD61+ H9oySvhdCjdHz4qL4WlNlX3V3znFY7mNFVj0k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=NDmJeCRqj7CCcDwr9z86hQsGograqrGWSUBUH2I8ZSGPqy8TDvtnzv6vxM9kVmtYFc cierjVENlOyvp7inhVRUPOKDmo46Wpj1yWZsNxAfAoJL7q5he5Rd4brKQxC10LIrYJjG scSUzY/yeXlwq0+H1pOlP3eTtGc1HV5v82QKI= MIME-Version: 1.0 Received: by 10.103.127.28 with SMTP id e28mr1924112mun.120.1251699445414; Sun, 30 Aug 2009 23:17:25 -0700 (PDT) Date: Mon, 31 Aug 2009 08:17:25 +0200 Message-ID: From: Vivien Malerba To: gnome-db list , gnome-announce-list@gnome.org, gnome-office-list@gnome.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [gnome-db] Libgda 4.0.4 released X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 06:17:46 -0000 I'm pleased to announce version 4.0.4 of Libgda, which is a maintenance release of the 4.0 serie. Short description: ------------------------ Libgda is a (relatively small) database access library: * a wrapper like ODBC but with more features to access several database engines * a general data model to use CVS or XML files * a meta data extractor (to know all about database objects in a comman way) * comes with an SQL console application (like mysql, psql or sqlite3 consoles) * relies on GLib, coded in C, its API is easy to use Changes from 4.0.3 --------------------------- - meta data corrections to the PostgreSQL provider - SQL rendering corrections Tarballs are available at http://ftp.gnome.org/pub/GNOME/sources/libgda/4.0 Pease note that Win32 archives are also available at http://ftp.gnome.org/pub/GNOME/binaries/win32/ See the http://live.gnome.org/ChooseLibgdaSQLite page for additionnal information about choosing between Libgda and SQLite when you need a database API. You can find more information at the projects' homepage (http://www.gnome-db.org), or you can ask any question/propose anything you want in the GNOME-DB mailing list, which is available at http://mail.gnome.org/mailman/listinfo/gnome-db-list From pochu27@gmail.com Sun Aug 30 23:51:57 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id 4227E7500C7 for ; Sun, 30 Aug 2009 23:51:57 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (firewall!) (up: 4479 hrs), (distance 17, link: (Google 2)), [74.125.78.25] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PES54aO418iB for ; Sun, 30 Aug 2009 23:51:50 +0000 (GMT) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by menubar.gnome.org (Postfix) with ESMTP id 6C938750117 for ; Sun, 30 Aug 2009 23:51:41 +0000 (GMT) Received: by ey-out-2122.google.com with SMTP id 22so685165eye.49 for ; Sun, 30 Aug 2009 16:51:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:x-enigmail-version:content-type; bh=Bo4uDIYmJK3VHsIfd1TIj0JWDEvsDzNwUXRgDINt048=; b=QfiWJ2O7I8BTH+DYGMQcK1aR7Zox/SZKvyg6NXvPQb74mWbtASa0eYNDaK6JN/t0CD TrvR9bQv6zKvDdipMFScEBagwKZdI/9tQbqnUyv9IaRM6b2pI5vDbRW0p0c7UVaotpz+ pRxFZu+pJ1filfxHpdkWkw02yuSFhm3CJeyoA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type; b=XncO5QLOI+AVPqYtnXchGXO9EBi0aG0sr4Bgye0xpvllV2/Fwrcot2S7WJAQf45AId +TOerghUX1lgx6ST/3qvzposyfPQuommzzhX1rrYgwaNwXKT9oUF1qVK645Yz9RGRq/Y v/ohR3Ko5NFFzeItv34FHtby9TanR6GJtfmfM= Received: by 10.216.0.79 with SMTP id 57mr988818wea.48.1251676299688; Sun, 30 Aug 2009 16:51:39 -0700 (PDT) Received: from ?192.168.2.103? (59.Red-81-44-62.dynamicIP.rima-tde.net [81.44.62.59]) by mx.google.com with ESMTPS id 10sm1065688eyd.10.2009.08.30.16.51.38 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Aug 2009 16:51:39 -0700 (PDT) Message-ID: <4A9B0EED.8050604@gmail.com> Date: Mon, 31 Aug 2009 01:44:45 +0200 From: Emilio Pozuelo Monfort User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701) MIME-Version: 1.0 To: gnome-db-list@gnome.org X-Enigmail-Version: 0.95.7 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1691A9B1EF0AFC13ED2A4949" X-Mailman-Approved-At: Mon, 31 Aug 2009 08:29:55 +0000 Subject: [gnome-db] libgnomedb future X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2009 23:51:57 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1691A9B1EF0AFC13ED2A4949 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ Please CC me on replies, I'm not subscribed ] Hi folks, I was wondering what are the plans for libgnomedb. Currently there are ma= ny 3.9x releases, but the last one doesn't build with libgda4 due to API changes = before the libgda 4 final release. The webpage currently states: "Starting with the upcoming 4.2 serie, GNOME-DB's production will be the = Libgda library which is mainly a database and data abstraction layer, and will i= nclude a GTK+ based UI extension (much of what the Libgnomedb was), and some gra= phical tools (making Mergeant irrelevant):" Does this mean libgnomedb and mergeant will be deprecated starting with l= ibgda 4.2? That is what Rodrigo suggested to me, although he wasn't completely = sure. If that's correct, is there a rough timeline for 4.2? Thanks! Emilio --------------enig1691A9B1EF0AFC13ED2A4949 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqbDu4ACgkQhTV17EoIsv6w/QCfXlT2TaQ92B4B2OW5zZw/y16Q z8UAnjevxM+wFXDr8p8FB4TX4HStrmg6 =X4lO -----END PGP SIGNATURE----- --------------enig1691A9B1EF0AFC13ED2A4949-- From vmalerba@gmail.com Mon Aug 31 08:36:05 2009 Return-Path: X-Original-To: gnome-db-list@gnome.org Delivered-To: gnome-db-list@gnome.org Received: from localhost (localhost.localdomain [127.0.0.1]) by menubar.gnome.org (Postfix) with ESMTP id CA99C75010A for ; Mon, 31 Aug 2009 08:36:05 +0000 (GMT) X-Virus-Scanned: by amavisd-new at gnome.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=2 tests=[BAYES_00=-2.599, TW_BG=0.077] X-Amavis-OS-Fingerprint: Linux 2.6 (newer, 2) (up: 4107 hrs), (distance 14, link: ethernet/modem), [209.85.220.215] Received: from menubar.gnome.org ([127.0.0.1]) by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEcFdvmBLLbd for ; Mon, 31 Aug 2009 08:36:00 +0000 (GMT) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by menubar.gnome.org (Postfix) with ESMTP id 8EC2B7500CD for ; Mon, 31 Aug 2009 08:35:50 +0000 (GMT) Received: by fxm11 with SMTP id 11so2634888fxm.15 for ; Mon, 31 Aug 2009 01:35:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=pzzdDcYOsyD7eDSya/KSz8TYFpIXhVppmnQWKHUUIc4=; b=EQZCCVMlKPlAAB6T0xlJxrEE5BPVnX26qXhsv95tk8gCgIFCrs3rnSjTlhYHOEpV/2 1Skk1EzzKGdIEjRfZiMEOa2VUqirNg3RS2AGmn8k/hYOQFP3xAMeK9G8nQuj9eLxMBcK k2nnj7RUtVkPAnODiCCG5l/+RVALgojIGLxzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vh1R3mbX+8hq9vSwU7zQXctvXZVGvXo9Gm+J2E4f9nYnQW7TmQ6mpH6kC1EhWW4UVs 2y0EgygiLBFV55H+E3R/yILFRCLUHbiZuYX81JCzGNj/EE7cxeblM42OSXfKTL+XLmX9 QlqBJ8V1aq6xpdSXentetE/+7aMD2TTkaQXss= MIME-Version: 1.0 Received: by 10.103.125.17 with SMTP id c17mr1995485mun.16.1251707748463; Mon, 31 Aug 2009 01:35:48 -0700 (PDT) In-Reply-To: <4A9B0EED.8050604@gmail.com> References: <4A9B0EED.8050604@gmail.com> Date: Mon, 31 Aug 2009 10:35:48 +0200 Message-ID: From: Vivien Malerba To: Emilio Pozuelo Monfort Content-Type: text/plain; charset=ISO-8859-1 Cc: gnome-db-list@gnome.org Subject: Re: [gnome-db] libgnomedb future X-BeenThere: gnome-db-list@gnome.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: GNOME-DB discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Aug 2009 08:36:06 -0000 2009/8/31 Emilio Pozuelo Monfort : > [ Please CC me on replies, I'm not subscribed ] > > Hi folks, > > I was wondering what are the plans for libgnomedb. Currently there are many 3.9x > releases, but the last one doesn't build with libgda4 due to API changes before > the libgda 4 final release. > > The webpage currently states: > > "Starting with the upcoming 4.2 serie, GNOME-DB's production will be the Libgda > library which is mainly a database and data abstraction layer, and will include > a GTK+ based UI extension (much of what the Libgnomedb was), and some graphical > tools (making Mergeant irrelevant):" > > Does this mean libgnomedb and mergeant will be deprecated starting with libgda > 4.2? That is what Rodrigo suggested to me, although he wasn't completely sure. Yes, he is right: from 4.2, there will only be one Libgda source archive containing Libgda, the UI extension replacing Libgnomedb and the GdaBrowser replacing (more or less) Mergeant. This is already in place with release 4.1.1. > > If that's correct, is there a rough timeline for 4.2? Most if not all of the new features are currently implemented in version 4.1.1, and only the GdaBrowser needs a bit more work because it can only for now be used to browse a database's structure. So, I think you can reasonably expect a few more 4.1.x versions with a 4.2 by the end of the year. Regards, Vivien