> -----Original Message-----
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 30 April 2002 18:32
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> 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.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
