> CTAS can be useful in some cases, Thanks for such feedback.
> but I can't imagine how we'd fit it into the Django ORM nicely. This is an usual challenge for such software extensions, isn't it? > There wouldn't be a model for the correspondingly created table. Can a data model be determined from its creation parameters? > Have you got a suggestion for the way you'd like to see it working? I published examples where data processing approaches are shown (also together with applications of the class library “SQLAlchemy”). I would like to be able to choose between the use of materialized views (or snapshots) and a concrete database table. How often will different development and software run time characteristics matter for these interfaces? Regards, Markus -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a460432c-495d-e6c1-4633-031f85bb5e0f%40web.de. For more options, visit https://groups.google.com/d/optout.
