On Tue, Dec 07, 2004 at 07:34:42PM -0500, Christopher Hicks wrote: > On Wed, 8 Dec 2004, Andy Hassall wrote: > >>>The fact still remains that the generic "Host" slot could > >>>be used for this purpose quite easily, as could the "DB" slot. > >> > >>I really really object to the DB slot being called DB. Oracle's term > >>"tablespace" is much less overused and confusing than database. > > > >But Oracle tablespaces have nothing to do with connecting; they're > >logical pools of storage only, and they play no part in name resolution. > >You can't specify a "tablespace" when connecting, you connect to an > >instance of a database, and you specify a user to authenticate as, which > >then determines which schema unqualified names refer to (by default). > > I'm talking about for the generic framework. When you connect to PG or > MySQL you connect to a database within an instance. Using the word > database there is confusing because database is such an abused term. > Since tablespace is a clear term that means what MySQL calls a database I > advocate using the less ambigous term. > > >So using "tablespace" in a DSN for Oracle would itself be confusing. > > So what? If its superfulous for Oracle so be it. If it gets passed to > Oracle after the connect as part of a "use" (or whatever the Oracle SQL > would be -- its been years since I was stuck fighting Ellison's baby) > that's fine too.
I've posted a patch to the docs. It's time to wind down this somewhat spralling thread now. Thanks for everyone's input. Now it's time for motivated people to make and send patches for their DBDs... Tim.
