So today I decided to try and bust out the patch and unit tests for
this ticket. The patch that was submitted last is pretty close other
than line numbers to get this working, HOWEVER.

The unit tests do not work.  When I apply the basic patch I am able to
enter the django shell, access the model, add entries and even run
syncdb.

The issue comes into play when I try to do a unit test. It
consistently says that my schema does not exist.  From what I can tell
since it is when create "test_mytable" runs, it also needs to be able
to create the schema that is set in the settings.DATABASE_SCHEMA
variable.  What is the best way/place to do this? I was thinking about
doing something like running a query like (select nspname from
pg_catalog.pg_namespace;) to determine if the schema exists. Obviously
this should only run on a test, and only one time.  I am not sure if
this should go in the django/db/backends/postgresql_psycopg2/base.py
or if it should go in the utils.py for tests (which it would make more
sense but wasn't able to determine what the best place for it would
be).

Anyhow this is something we want to add so we can use a schema for the
entire project (not apps like the ticket said is out of scope).

Any info / comments would be great. I am still new to python coding,
but figured I would give this a whirl anyhow.

Andy Holman


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to