That sounds like a very useful feature - gets my vote. Will have another go at getting django to read a view with mysql - could well be a silly error of mine causing the problem.
On Jan 17, 10:47 am, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Sat, 2009-01-17 at 02:14 -0800, phoebebright wrote: > > I say an earlier post that seemed to imply they did. > > > I created a view in an existing db and wrote a model test to match it > > so syncdb works fine. > > Hm ... it just occurred to me: whilst running syncdb probably works if > you've specified Meta.db_table correctly (it won't create anything), you > want to be careful running management commands against that app (e.g. > reset or sqlclear). > > In the future (hopefully for Django 1.1 if I get time; it's not hard, > just needs some polishing), there'll be a parameter for Meta that > effectively tells Django "don't ever delete/create/flush the table for > this model. I'm admin'ing it manually". It's designed for things like > views. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
