Russell Keith-Magee wrote: > I just created a test model and set the db_table to 'poll.polls', and > tables were created without difficulty. What problem did you > experience? > Problem is that django quotes db_table so table is called "poll.polls" and postgres stores it in default schema "public" so it is nemed as public."poll.polls". What I want is to quote it like "poll"."polls" so it will be stored in schema "poll" as table "polls". I use 0.95 but I assume that svn version behaves the same.
Some food for thought: >> 1) There is the issue of compatibility with existing deployed >> projects. This isn't necessarily a show stopper, but a change like >> this isn't something that would be done on a whim - there would have >> to be a compelling argument. >> The only thing I can figure out is to add it to settings.py as an option. With that option django should use schema instead of prefixes by dafult, otherwise it should allow using schema just manually by db_schema in Meta class. >> 2) There is the issue of consistency between database backends. Django >> is database agnostic, so there shouldn't be any big surprises (such as >> fundamental changes in database table naming policies) as a result of >> changing backends. >> Solution for food #1 would make apps DB independent. In worst case (that is using db_schema in Meta) schema noncapable Dbs could use that as a prefix for db_table. Does it make sense? >> 3) If Django is going to support schema, I would suggest that it >> should be at more than just a cosmetic level - manage.py should be >> creating schema on a per app/per project basis. >> That will be more than sufficient :) >> I can't say this particular issue hits any of my particular itches. >> However, if it is something you are interested in, open a ticket, >> suggest some patches, and ask for comment on the developers mailing >> list. Ideas and suggestions are great, but code speaks volumes :-) >> >> As I mentioned before I i'm newbie in django and also "perfectionist with DEADLINES", but I will give it the try :) Thank you for your time, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
