#6148: Add generic support for database schemas
-------------------------------------+-------------------------------------
Reporter: ikelly | Owner: akaariai
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Design
Keywords: oracle postgresql | decision needed
mysql schemas | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I won't likely make it to !DjangoCon. But, I will try to keep track of
work done in this ticket.
As for now, I think the most important thing is to get the way databases
are set up (both the settings side, and how production/test databases are
handled) correct.
I am not 100% sure if I understand the routers idea... Still, having the
model's opts at hand in the compiler would be nice, there are other uses
for that, too.
--
Ticket URL: <https://code.djangoproject.com/ticket/6148#comment:135>
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 https://groups.google.com/groups/opt_out.
