#77 closed enhancement (wontfix)
The PostgreSQL code should use schemas instead of prefixes for namespaces.
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | |
Severity: | minor | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Rather than append App_ before every table in PostgreSQL, you should use Schemas http://www.postgresql.org/docs/8.0/static/ddl-schemas.html. That's what they're there for, and it makes the database much more readable.
Change History (6)
comment:1 by , 19 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
priority: | normal → high |
---|---|
Resolution: | wontfix |
Severity: | normal → major |
Status: | closed → reopened |
Type: | defect → enhancement |
Both PostgreSQL and Oracle support schemas, it should also be supported by django. I want to use this application but can not in it's current form.
comment:3 by , 18 years ago
priority: | high → normal |
---|---|
Severity: | major → normal |
Please provide an implementation if you'd like to see this feature in Django.
comment:4 by , 18 years ago
priority: | normal → lowest |
---|---|
Severity: | normal → minor |
comment:5 by , 18 years ago
Triage Stage: | Unreviewed → Accepted |
---|
Adrian has asked for a patch, will YOU be the one that writes it? ;)
comment:6 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Triage Stage: | Accepted → Design decision needed |
Using schemas for each app would make little sense as you'd just end up with a bunch of schemas. Optional support for schemas -- a la #1051 -- is a much better idea.
This isn't a big enough problem to merit the special-casing of PostgreSQL. We've used the current method for a couple of years and haven't had any problems.