frontend.db: Adding afe custom database engine
commit06c16da75060e0e48a6d1bf5eaaeeb804620aa12
authorlmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4>
Mon, 6 Jun 2011 17:40:56 +0000 (6 17:40 +0000)
committerlmr <lmr@592f7852-d20e-0410-864c-8624ca9c26a4>
Mon, 6 Jun 2011 17:40:56 +0000 (6 17:40 +0000)
tree9d03af069d9f163ac477e6de49fbd9d78af88ce2
parent69fe1942edd09f377b930f9f44e1413e9f75cbab
frontend.db: Adding afe custom database engine

Turns out that we rely on custom code to generate
joins that does some trickery with Django ORM system,
and was using a method calling get_from_clause, that
was present on the Query class on Django 1.1. Now,
the method was moved to a class upper in the hierarchy,
called SQLCompiler, and SQLCompiler is tied to the db
backend being used. After some research, seems like there's
no solution cleaner than implementing one db backend
special for autotest, just to accomodate this function.

So created one db engine that inherits pretty much everything
from the mysql one, except for the compiler classes.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@5408 592f7852-d20e-0410-864c-8624ca9c26a4
frontend/db/__init__.py [new file with mode: 0644]
frontend/db/backends/__init__.py [new file with mode: 0644]
frontend/db/backends/afe/__init__.py [new file with mode: 0644]
frontend/db/backends/afe/base.py [new file with mode: 0644]
frontend/db/backends/afe/compiler.py [new file with mode: 0644]
frontend/db/backends/afe/creation.py [new file with mode: 0644]
frontend/db/backends/afe/introspection.py [new file with mode: 0644]
frontend/db/backends/afe/validation.py [new file with mode: 0644]