> Answering line by line is not really a good use of either of our time I increased my feedback according to the provided information.
> and I apologize that I cannot really work with the lack of specifics > presented here, You might prefer an other communication style. > if I can restate the situation, the "CREATE TABLE AS" use case > is not very common, Other usage patterns can be more popular. > and as far as an ORM use case, I have no idea what such a feature > would look like. The design of additional classes is an usual challenge for corresponding software development, isn't it? > The SQL component of CREATE TABLE AS is very easy to create as a recipe The construction of such a SQL command might be reasonable. > and since it is very idiosyncratic to specific databases The variations in SQL support are interesting somehow, aren't they? > there is not a compelling reason to prioritize designing and maintaining a > built in construct, I can follow such a view to some degree. > but as always, contributors are welcome to propose I suggested a clarification for software aspects in this direction. > and assist in implementing specific Core and ORM-level features. I am curious under which circumstances further software extensions will become more feasible. > Specific proposals and test cases are the most helpful approach. Can you imagine a need for table creations because of data processing requirements and known consequences from query run time characteristics? Regards, Markus -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
