17 messages in com.mysql.lists.gui-toolsRe: Select between two servers| From | Sent On | Attachments |
|---|---|---|
| Tom Achtenberg | 22 Jul 2003 09:50 | |
| Adam Hooper | 22 Jul 2003 10:01 | |
| Tom Achtenberg | 22 Jul 2003 10:04 | |
| Chad...@cexp.com | 22 Jul 2003 11:05 | |
| Adam Hooper | 22 Jul 2003 11:23 | |
| Tom Achtenberg | 22 Jul 2003 11:27 | |
| Adam Hooper | 22 Jul 2003 11:32 | |
| Adam Majer | 22 Jul 2003 22:58 | |
| Adam Hooper | 23 Jul 2003 04:33 | |
| Tom Achtenberg | 23 Jul 2003 07:18 | |
| Adam Hooper | 23 Jul 2003 07:20 | |
| Adam Majer | 24 Jul 2003 15:44 | |
| Adam Hooper | 24 Jul 2003 17:20 | |
| Tom Achtenberg | 25 Jul 2003 07:37 | |
| Adam Hooper | 25 Jul 2003 07:39 | |
| Adam Majer | 25 Jul 2003 09:55 | |
| Adam Majer | 25 Jul 2003 09:59 |
| Subject: | Re: Select between two servers |
|---|---|
| From: | Adam Hooper (ada...@densi.com) |
| Date: | 07/24/2003 05:20:46 PM |
| List: | com.mysql.lists.gui-tools |
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 ada...@densi.com