Author: Alex
Date: 2009-06-18 19:35:35 -0500 (Thu, 18 Jun 2009)
New Revision: 11077
Modified:
django/branches/soc2009/multidb/TODO.txt
Log:
[soc2009/multidb] Updated the TODO to more accurately reflect the current state
of things.
Modified: django/branches/soc2009/multidb/TODO.txt
===================================================================
--- django/branches/soc2009/multidb/TODO.txt 2009-06-19 00:29:18 UTC (rev
11076)
+++ django/branches/soc2009/multidb/TODO.txt 2009-06-19 00:35:35 UTC (rev
11077)
@@ -5,7 +5,7 @@
that need to be done. I'm trying to be as granular as possible.
-2) Update all old references to ``settings.DATABASE_*`` to reference
+1) Update all old references to ``settings.DATABASE_*`` to reference
``settings.DATABASES``. This includes the following locations
* ref/settings -- needs to be upddated for TEST_*
@@ -16,34 +16,26 @@
Replace old instances of :setting:`DATABASE_` with a new tag or something.
-3) Update all management commands in the following way:
+2) Update all management commands in the following way:
* ``dumpdata``: By default dump the ``default`` database. Later add a
``--database`` flag.
flush, reset, and syncdb need to not prompt the user multiple times.
-7) Remove any references to the global ``django.db.connection`` object in the
+3) Remove any references to the global ``django.db.connection`` object in the
SQL creation process. This includes(but is probably not limited to):
* The way we create ``Query`` from ``BaseQuery`` is awkward and hacky.
+ * ``Field.get_db_prep_lookup``
+ * ``DateField.get_db_prep_value``
+ * ``DateTimeField.get_db_prep_value``
+ * ``DecimalField.get_db_prep_save``
+ * ``TimeField.get_db_prep_value``
+4) Wait on the merge of the m2m stuff.
+
5) Add the ``using`` Meta option. Tests and docs(these are to be assumed at
each stage from here on out).
-8) Implement some way to create a new ``Query`` for a different backend when
- we switch. There are several checks against ``self.connection`` prior to
- SQL construction, so we either need to defer all these(which will be
- difficult, but probably not impossible), or have an alternate strategy,
- such as:
-
- * Remove all tests against ``Query.connection`` before the SQL generation
- phase. This involves changing the following methods:
-
- * ``Field.get_db_prep_lookup``
- * ``DateField.get_db_prep_value``
- * ``DateTimeField.get_db_prep_value``
- * ``DecimalField.get_db_prep_save``
- * ``TimeField.get_db_prep_value``
-
-10) Time permitting add support for a ``DatabaseManager``.
+6) Time permitting add support for a ``DatabaseManager``.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
