From 99fdf66600973c67f634cce79a009c2139f33ee7 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Thu, 18 Jun 2009 23:42:00 +0000 Subject: [PATCH] [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 --- TODO.TXT => TODO.txt | 8 -------- 1 file changed, 8 deletions(-) rename TODO.TXT => TODO.txt (80%) diff --git a/TODO.TXT b/TODO.txt similarity index 80% rename from TODO.TXT rename to TODO.txt index ef20dffb5c..3c1b577a6a 100644 --- a/TODO.TXT +++ b/TODO.txt @@ -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): * 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 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 phase. This involves changing the following methods: - * ``Query.add_aggregate`` * ``Field.get_db_prep_lookup`` * ``DateField.get_db_prep_value`` * ``DateTimeField.get_db_prep_value``