We all inherit less-than-ideal situations. If this is running once a day and isn't impacting performance or other work, I wouldn't really worry about the huge join matrix. It sounds like the current solution is "good enough". In a few weeks or months you'll be better acquainted with SqlAlchemy and Sql in general and can revisit.
In terms of your 15minute script: When you can use subqueries, filters and `load_only` for certain columns, your backend will generate a smaller matrix and there will be a less data transferred "over the wire". -- 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.
