Re: AW: Re: MySQL and BerkleyDB (fwd)

On Mon, 22 Jan 2001, Zeugswetter Andreas SB wrote:

>
> > Is anyone looking at doing this? Is this purely a MySQL-ism, or is it
> > something that everyone else has except us?
>
> We should not only support access to all db's under one postmaster,
> but also remote access to other postmaster's databases.
> All biggie db's allow this in one way or another (synonyms,
> qualified object names) including 2-phase commit.
> Ideally this includes access to other db manufacturers, flat files, bdb ...
> Meaning, that this is a problem needing a generic approach.

Of course, a generic, powerful approach would be great.

However, a simple, limited approach would a be solution for (I
suspect) 97% of the cases, which is that one software package creates a
database to store mailing list names, and another creates a database to
store web permissions, and you want to write a query that encompasses
both, w/o semi-tedious COPY TO FILEs to temporarily move a table back and
forth. And of course, a simple solution might be completed faster :-)

How could this be handled?

* a syntax for db-table names, such as mydb.myfield or something like
that. (do we have any unused punctuation? :-) )

* aliases, so that tblFoo in dbA can be called as ToFoo in dbB

* other ways?

The second might be easier from a conversion view: the user wouldn't have
to understand that this was a 'link', but it might prove complicated when
there are many links to keep track of, etc.

--
Joel Burton <jburton(at)scw(dot)org>
Director of Information Systems, Support Center of Washington