--- Rob Butler <robert.butler5@verizon.net> wrote:
> I disagree, The cross-db operations would indeed be very nice to
> have, but you COULD make things work across DB's from within your
> application code if Postgres supported 2PC. Granted this would not
> be the best, but it could be done.
Sure, anything could be done given time and money. OTOH, why would one
want to hand-code joins between tables in different dbs, configure
multiple connection pools, etc when all that can be avoided with a
RDBMS that supports cross-db operations? And since mySql supports
cross-db ops now, mySql could become a very intersting option when they
implement all the features they promissed for version 5.0
> Also, if you want to start doing cross-db operations you will need
> 2PC to support this. While 2PC may not be needed to support cross-db
> operations on two db's on the same server, it would definetly be
> needed to do cross-db operations with db's on two separate servers.
> Why limit the cross-db operations only to db's on the same server?
I'm not saying Postgres has to limit itself to cross-db ops on the same
server only. However, if it's much simpler to implement then why not
start there? Cross-db ops have been on the Postgres TODO list for
several years now and, AFAICT, it does not appear that they will be
available any time soon. Thanks
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
