After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 130837 - gnome_db_browser doesn't handle namespaces
gnome_db_browser doesn't handle namespaces
Status: RESOLVED OBSOLETE
Product: libgda
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: malerba
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-08 00:08 UTC by Jon Willeke
Modified: 2008-03-14 12:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jon Willeke 2004-01-08 00:08:01 UTC 
I'm using the following: libgda 1.0.2, libgnomedb 1.0.2, Python 2.3.3,
PyGTK 2.0.0, unixODBC 2.2.7, PostgreSQL 7.3.2, and psqlodbc 07.03.0200.

The gnome_db_browser widget doesn't seem to handle namespaces.  I have a
PostgreSQL database with two tables: public.foo and jw.foo.  When I use the
PostgreSQL provider, I see only public.foo as foo.  When I use the ODBC
provider, I see two foo tables with the characteristics of public.foo.  (I
see similar behavior connecting via ODBC to a proprietary DBMS.)  By
comparison, WinSQL displays public.foo and jw.foo separately, using their
full names.

I am using home-grown Python bindings, but I think the problem actually
lies with libgnomedb, libgda, or the providers.
Comment 1 Murray Cumming 2007-01-16 17:32:30 UTC 
We will need some kind of test case, ideally with the C API, and ideally with the latest libgnomedb API version.
Comment 2 Murray Cumming 2008-03-14 10:59:29 UTC 
I'll close this bug as obsolete soon unless someone provides a test case, in C please. We can't fix bugs that we can't reproduce.
Comment 3 Jon Willeke 2008-03-14 12:50:44 UTC 
I'm sorry, but it's just been too long.  I'm not using libgnomedb, and I don't have any of this set up.  As I recall, there isn't much of a test case to provide--most of the work is in setting up the database.  If no one wants to investigate, you may as well close this.
Comment 4 Murray Cumming 2008-03-14 12:54:33 UTC 
OK. Thanks for the reply, and sorry on behalf of whoever was tending these bugs back then.