Thread: Re: [INTERFACES] Schemas: status report, call for developers
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 30 April 2002 18:32 > To: pgsql-hackers@postgresql.org; pgsql-interfaces@postgresql.org > Subject: [INTERFACES] Schemas: status report, call for developers > > > Current CVS tip has most of the needed infrastructure for > SQL-spec schema support: you can create schemas, and you can > create objects within schemas, and search-path-based lookup > for named objects works. There's still a number of things to > be done in the backend, but it's time to start working on > schema support in the various frontends that have been broken > by these changes. I believe that pretty much every frontend > library and client application that looks at system catalogs > will need revisions. So, this is a call for help --- I don't > have the time to fix all the frontends, nor sufficient > familiarity with many of them. > > JDBC and ODBC metadata code is certainly broken; so are the > catalog lookups in pgaccess, pgadmin, and so on. psql and > pg_dump are broken as well (though I will take responsibility > for fixing pg_dump, and will then look at psql if no one else > has done it by then). I'm not even sure what else might need > to change. > Thanks Tom, this is just the post I've been waiting for! To anyone thinking of hacking pgAdmin at the moment -> now would probably not be the best time as I will be *seriously* restructuring pgSchema. Regards, Dave.
> > JDBC and ODBC metadata code is certainly broken; so are the > > catalog lookups in pgaccess, pgadmin, and so on. psql and > > pg_dump are broken as well (though I will take responsibility > > for fixing pg_dump, and will then look at psql if no one else > > has done it by then). I'm not even sure what else might need > > to change. phpPgAdmin (WebDB) will be broken as well. I think myself and at least a few other committers lurk here tho. Other things that will break: TOra Various KDE interfaces Chris
On Wed, May 01, 2002 at 10:05:23AM +0800, Christopher Kings-Lynne wrote: > > phpPgAdmin (WebDB) will be broken as well. I think myself and at least a > few other committers lurk here tho. > > Other things that will break: > > TOra > Various KDE interfaces GNUe will break, as well. Ross
I think it would be much faster simply to list of the programs that use Postgresql internals that won't break. -- Rod ----- Original Message ----- From: "Ross J. Reedstrom" <reedstrm@rice.edu> To: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> Cc: "Dave Page" <dpage@vale-housing.co.uk>; "Tom Lane" <tgl@sss.pgh.pa.us>; <pgsql-hackers@postgresql.org>; <pgsql-interfaces@postgresql.org>; <pgadmin-hackers@postgresql.org> Sent: Tuesday, April 30, 2002 11:28 PM Subject: Re: [HACKERS] [INTERFACES] Schemas: status report, call for developers > On Wed, May 01, 2002 at 10:05:23AM +0800, Christopher Kings-Lynne wrote: > > > > phpPgAdmin (WebDB) will be broken as well. I think myself and at least a > > few other committers lurk here tho. > > > > Other things that will break: > > > > TOra > > Various KDE interfaces > > GNUe will break, as well. > > Ross > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >
"Ross J. Reedstrom" <reedstrm@rice.edu> writes:
> GNUe will break, as well.
Do I hear a volunteer to fix it?
regards, tom lane
"Rod Taylor" <rbt@zort.ca> writes:
> I think it would be much faster simply to list of the programs that
> use Postgresql internals that won't break.
Approximately none, I'm sure :-(. This thread isn't about that, it's
about stirring up the troops to fix everything that must be fixed.
regards, tom lane
On Wed, May 01, 2002 at 12:03:00AM -0400, Tom Lane wrote: > "Ross J. Reedstrom" <reedstrm@rice.edu> writes: > > GNUe will break, as well. > > Do I hear a volunteer to fix it? I'm willing to implement whatever clever solution we all come up with. I'll have to coordinate w/ the GNUe IRC folks to get it checked in. Ross
"Ross J. Reedstrom" <reedstrm@rice.edu> writes:
>>> GNUe will break, as well.
> I'm willing to implement whatever clever solution we all come up with.
If you need help in inventing a solution, it'd be a good idea to explain
the problem. Personally I'm not familiar with GNUe ...
regards, tom lane
On Wed, May 01, 2002 at 12:56:00AM -0400, Tom Lane wrote: > "Ross J. Reedstrom" <reedstrm@rice.edu> writes: > >>> GNUe will break, as well. > > I'm willing to implement whatever clever solution we all come up with. > > If you need help in inventing a solution, it'd be a good idea to explain > the problem. Personally I'm not familiar with GNUe ... I think all the interfaces are having the same fundemental problem: how to limit the tables 'seen' to a particular list of schema (those in the path). GNUe is GNU Enterprise System - a somewhat grandiose name for a business middleware solutions project. It's highly modular, with a common core to deal with things like DB access. There's a reasonably nice forms designer to handle quickie 2-tier DB apps (client-server, skip the middleware). Right now, it's mostly coded in python. I'm taking off on a business trip for the remainder of the week, starting tomorrow (err today?!) morning. I'll take the GNUe code along and see what it's db schema discovery code is actually doing, and think about what sort of clever things to do. I think for GNUe, we might get away with requiring the end-user (designer) to select a particular schema to work in, and then just qualify everything. Later, Ross