Re: Connection.setCatalog()
| От | jason@netspade.com |
|---|---|
| Тема | Re: Connection.setCatalog() |
| Дата | |
| Msg-id | 5438518.995326461799.JavaMail.jason@www2.kc.aoindustries.com обсуждение |
| Ответ на | Connection.setCatalog() (jason@netspade.com) |
| Список | pgsql-jdbc |
[[[ Original Message from Tom Lane <tgl@sss.pgh.pa.us> ]]] > jason@netspade.com writes: > > Do you know whether PostgreSQL will support the catalogname.tablename > > syntax in SQL queries in the future? > > Schema support is on the to-do list. It's probably too late to imagine > that it will get done for 7.2, but maybe for 7.3. > > Although the details haven't been argued out yet, I suspect that the > existing concept of independent databases within an installation will > remain in place (for backwards compatibility if nothing else). > SQL-style schemas and catalogs will exist as new naming levels > *within* what we now call a database. I see - I didn't realise this. As this is the case, there is no need for my database tool to list available databases sincedatabases in postgresql are clusters. Thanks for clarifying that. > Peter E. has previously commented that Postgres databases correspond > most closely to the SQL concept of "catalog cluster", not "catalog". > This agrees with my reading of SQL92 4.13: > > A cluster is an implementation-defined collection of catalogs. > Exactly one cluster is associated with an SQL-session and it > defines the totality of the SQL-data that is available to that > SQL-session. > > Schemas and catalogs will exist within a database, and there will > still be no possibility of cross-database accesses (but, hopefully, > much less need for it either). Good. As long as everything conforms to some kind of standard we're okay :) > While I haven't followed this discussion closely, it appears to me that > you are trying to make setCatalog reconnect to a new database --- ie, a > new cluster in SQL terminology. I think this is a bad idea, as it will > create a backwards compatibility problem once we have actual catalogs > for setCatalog to work with. I'd suggest that the right short-term > thing is for setCatalog to either do nothing or throw an error. I agree. In which case the update Peter E did to DatabaseMetaData.getCatalogs() should be backed out. At least I've learnthow to use CVS and how to make context diffs :) > > regards, tom lane Jason Davies jason@netspade.com
В списке pgsql-jdbc по дате отправления: