Opened 15 years ago

Closed 14 years ago

Last modified 13 years ago

#77 closed enhancement (wontfix)

The PostgreSQL code should use schemas instead of prefixes for namespaces.

Reported by: RahmCoff@… 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


Rather than append App_ before every table in PostgreSQL, you should use Schemas That's what they're there for, and it makes the database much more readable.

Change History (6)

comment:1 Changed 15 years ago by Adrian Holovaty

Resolution: wontfix
Status: newclosed

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.

comment:2 Changed 14 years ago by j.states@…

priority: normalhigh
Resolution: wontfix
Severity: normalmajor
Status: closedreopened
Type: defectenhancement

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 Changed 14 years ago by Adrian Holovaty

priority: highnormal
Severity: majornormal

Please provide an implementation if you'd like to see this feature in Django.

comment:4 Changed 14 years ago by Oliver Beattie <oliver@…>

priority: normallowest
Severity: normalminor

comment:5 Changed 14 years ago by Chris Beaven

Triage Stage: UnreviewedAccepted

Adrian has asked for a patch, will YOU be the one that writes it? ;)

comment:6 Changed 14 years ago by Jacob

Resolution: wontfix
Status: reopenedclosed
Triage Stage: AcceptedDesign 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.

Note: See TracTickets for help on using tickets.
Back to Top