Dear list...
I'm currently starting a larger project and want to use Django for it.
First order of business was creating the necessary database schema with
pgadmin3 (a PostgreSQL GUI). Next thing after setting my settings.py right
was to run "django-admin inspectdb" to get my already existing database
schema into a models.py. Unfortunately the models.py was mostly empty. I
figured out it's due to my use of PostgreSQL schemas. Django just didn't
find my tables.
/*
Where other DBMS like MySQL just have databases and tables you can use an
additional layer to seperate different applications or parts of your
application into schemas. Where in MySQL you have database->table you have
database->schema->table in PostgreSQL. You query them through e.g.
SELECT * from schemaname.tablename;
You may think of those schemas just as different namespaces. The default
namespace is 'public' and automatically prepended through a search path
variable.
*/
The problem has been raised in
- http://code.djangoproject.com/ticket/1051
- http://code.djangoproject.com/ticket/1208
already.
I'm running Django 0.95 on Debian.
Did anyone else find a workaround? Is it meanwhile possible to use at least
a models.py without using "inspectdb"? My experiments
with 'schemaname.tablename' just lead me
to "public"."schemaname.tablename" which is obviously not what I want.
I'd like to hear comments. Or is PostgreSQL an uncommon DBMS to use with
Django? (btw, is there a reason to prefer psycopg over psycopg2?) I can of
course restrain myself to the "public" schema but my application would
benefit from different schemas.
Kindly
Christoph
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
