> True, there are instances where you would want to have different databases
> and join b/w them. I use that all the time.
>
> But I still don't understand *how* you can join resuls from different
> databases. That would require you to send a command to one server,
> that server automagically connects to another, runs a sub-query to get
> some results specific to "the other" server, and finally run a query on
> itself and join the results. Lastly, the data gets returned to the
> user....
>
> *BUT* my objections would be:
You're right: it's the kind of thing that sells because people THINK
they want it, when they really want a more elegant solution. You've
described exactly how SQL server does it. And it is pretty nifty. But
there are HUGE security implications, and I've had numerous critical
bugs connecting to a MySQL server and two Access databases (i.e., simply
stops working).
The whole thing reeks of "hack-job"-ness, and I'd agree that MySQL
should steer clear unless a very elegant solution appears (is that
possible?). But it's useful :)
Adam Hooper
adamh@stripped
