On Jan 26, 3:22 am, Russell Keith-Magee <russ...@keith-magee.com> wrote: > Django doesn't have a built-in representation of a view. .. > > You can define a Django model as a wrapper around a view by marking it > managed, but that doesn't make the model read-only -- it just prevents > Django from trying to create the model during syncdb.
Ok, thanks for this clear answer. I've noted the "managed" option that might avoid errors on a sync but as django still thinks these tables are updateable it's not a real solution - and it's not wise to recommend django for the situations mentioned in my first post. So the django ORM is in the same situation as the Ruby-on-Rails ORM. But, as opposed to Ruby, a possible solution already exists in the form of SQLalchemy. This approach has already been followed: http://code.google.com/p/django-sqlalchemy/ Progress in this project seems a bit low, but maybe one day some enlighted ghosts will take up the torch ... -- 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.
