[gnome-db] Problem with sqlite provider in 4.0.1

I wonder how the libgda sqlite provider works on Linux.  On FreeBSD, we
are currently building it with the system sqlite3, but this appears to
be broken.  The code assumes an older version of the libgda-column API.
See this excerpt from gda-sqlite-provider.c:

                        gda_column_set_description (0, "name");
                        gda_column_set_name (0, "name");
                        gda_column_set_g_type (0, G_TYPE_STRING);
                        gda_column_set_description (1, "nargs");
                        gda_column_set_name (1, "nargs");
                        gda_column_set_g_type (1, G_TYPE_INT);
                        gda_column_set_description (2, "specificname");
                        gda_column_set_name (2, "specificname");
                        gda_column_set_g_type (2, G_TYPE_STRING);

That code triggers a segmentation fault in libgda when executed as 0x1
is an invalid memory address (i.e., not a GdaColumn).  However, if we
build libgda using the built-in sqlite, the problem is not seen.

I'm wondering what is the preferred way to build libgda, and if Linux is
currently using the embedded sqlite, or somehow working around this API
mismatch problem.  Thanks.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team      ::      [email protected]
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome

_______________________________________________
gnome-db-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-db-list

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAknndiQACgkQb2iPiv4Uz4fo3wCdGqJ7UbEDAf412CGUTUWQz/TT
jwsAn2QakzLY7EPLu9Q01n+rMDIHOAh6
=hQVf
-----END PGP SIGNATURE-----