On Apr 14, 2006, at 6:54 PM, Ed Epstein wrote:
> > Adrian Holovaty wrote: > >> That's the big question -- should the schema be specified in the >> settings file or in the model? (Well, I've never used schemas, so >> maybe it's not as big of a question as I'm making it out to be. Maybe >> it doesn't make sense to put the schema in the model?) > > Well here's the thing: I've not been using Django for very long, but > I've found the project / app dichotomy both useful and confusing. One > of the more confusing aspects of it is how the model table names are > constructed with the app name as a prefix. What you often end up with > (and I think this is in the tutorial) is something like "poll_polls" > and whatnot as table names. This doesn't seem very user-friendly to > me. > I've been using Postgres for a few years now and I've not felt the need to use schemas. I also didn't like the names that Django gave to my tables. But of course you can name them anything you'd like using the db_table field of the META inner class. A little more effort, but this comes in handy when using legacy databases. Don --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
