1
0
mirror of https://github.com/django/django.git synced 2025-07-05 18:29:11 +00:00

[soc2009/multidb] Updated TODO to bring it up to date with the current state

git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2009/multidb@11074 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Alex Gaynor 2009-06-18 23:42:00 +00:00
parent 4f461542b5
commit 99fdf66600

View File

@ -27,13 +27,6 @@ that need to be done. I'm trying to be as granular as possible.
SQL creation process. This includes(but is probably not limited to): SQL creation process. This includes(but is probably not limited to):
* The way we create ``Query`` from ``BaseQuery`` is awkward and hacky. * The way we create ``Query`` from ``BaseQuery`` is awkward and hacky.
* ``django.db.models.fields.Field`` This uses it, as do it's subclasses.
* ``django.db.models.fields.related`` It's used all over the place here,
including opening a cursor and executing queries, so that's going to
need to be totally refactored. There's a ticket to at least move that
raw SQL and execution to ``Query``/``QuerySet`` so hopefully that makes
it in before I need to tackle this.
5) Add the ``using`` Meta option. Tests and docs(these are to be assumed at 5) Add the ``using`` Meta option. Tests and docs(these are to be assumed at
each stage from here on out). each stage from here on out).
@ -47,7 +40,6 @@ that need to be done. I'm trying to be as granular as possible.
* Remove all tests against ``Query.connection`` before the SQL generation * Remove all tests against ``Query.connection`` before the SQL generation
phase. This involves changing the following methods: phase. This involves changing the following methods:
* ``Query.add_aggregate``
* ``Field.get_db_prep_lookup`` * ``Field.get_db_prep_lookup``
* ``DateField.get_db_prep_value`` * ``DateField.get_db_prep_value``
* ``DateTimeField.get_db_prep_value`` * ``DateTimeField.get_db_prep_value``