Fix frontend afe readonly connection
commit65bc204c024f61002dd4d1fe09b03a5561a1e143
authorlmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4>
Wed, 1 Jun 2011 17:48:27 +0000 (1 17:48 +0000)
committerlmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4>
Wed, 1 Jun 2011 17:48:27 +0000 (1 17:48 +0000)
treecbf07a2ea97c661f7c81e7fbd7729cb933219bd1
parent90123972ea31e6fa1cb6fe353bedb7baa928bc0c
Fix frontend afe readonly connection

I think this is a bug on frontend/afe/readonly_connection for a long time.
Maybe nobody really looked at it. In short, the readonly connection
never talked to the readonly databased based on global_config.ini's
readonly db configuration.

This patch should fix it properly.

Changes from v1:
* Fix a comparison among self._connection and django.connection. The
intended comparison was among self._connection and
django.connection.connection. This other bug has gone unnoticed because
of the first bug Eric fixed.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Signed-off-by: Eric Li <ericli@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@5392 592f7852-d20e-0410-864c-8624ca9c26a4
frontend/afe/readonly_connection.py