Sounds like a transaction server to me.
Curtis John Masterson said: > Situation: mass virtual website hosting, with php/perl/python. One > master mysql server, one or more replicated slaves. > > Question: would it be possible/feasible to write a daemon that accepts > connections on behalf of mysqld, and depending on what type of query it > is (updating or selecting) farm the query out to the appropriate > database server? Perhaps it could do some connection pooling as well. > > > The reason: we'd like to keep telling our users to connect to "the > database server", instead of hoping that they will always write correct > code and connect to the appropriate servers, which of course they > won't. > > Any feedback (such as, "that's the stupidest idea I've ever heard, why > don't you just do _____") would be appreciated :) > > > > John Masterson > Modwest > Powerful, Affordable Web Hosting > http://www.modwest.com > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> To > unsubscribe, e-mail > <[EMAIL PROTECTED]> Trouble > unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
