#12308: Adding tablespace support to postgres backends -------------------------------------+------------------------------------- Reporter: tclineks | Owner: aaugustin Type: New | Status: new feature | Component: Database layer Milestone: | (models, ORM) Version: SVN | Severity: Normal Resolution: | Keywords: Triage Stage: Accepted | Has patch: 1 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -------------------------------------+-------------------------------------
Comment (by aaugustin): Replying to [comment:19 akaariai]: > Maybe I am taking the "ready for checkin" a bit too literally? :) You aren't; "ready for checkin" means "if I were a core developer, I'd commit this patch as is". Unless the problem is trivial (like a typo in the docs), there must be an exact patch, to avoid wasting the time of the core developers who commits the patch. ---- I ran the tests under Oracle 10g, and they failed because tablespace names are capitalized by the Oracle backend. I fixed this bug and re-ran the tests under SQLite, PostgreSQL, MySQL and Oracle; they pass everywhere. I'm uploading a new patch that adresses this problem, your two remaining remarks, and also removes a trailing space. To represent the new, empty file, I created a diff in git format, but it still doesn't work with `patch -p1`, use `git apply` instead. -- Ticket URL: <https://code.djangoproject.com/ticket/12308#comment:20> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- 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.