We've discussed this and generally it does sound like a good idea, but
will more than likely have to wait till 2.0 time.
The more ideal solution, IMO, is if you are using mysql, to use the
mysql proxy solution. That way, it is transparent to your application
and actually handled at a more robust layer in the stack (the database
itself).
-ralph
Jean-Michel ANDRE wrote:
> Hi,
>
> Sorry if this question has already been addressed (actually I've found this
> :
> http://www.nabble.com/OOP-Design-question-related-to-Zend_Db_Adapter-to21754
> 135.html, but nobody answered to william0275).
>
> I would like to provide an abstraction layer so that read db queries would
> be routed to one server (say A) and write queries to another server (say B),
> so that it is completely transparent to developers (they would continue to
> use $db->select(), $db->insert(), $db->update() and $db->query() as usual) .
> Is there a classical solution for that ?
>
> Jean-Michel
>
>
没有评论:
发表评论