I'm sure there's a great reason for this, but why does the new selectin loader join the parent table and use the parent ids instead of using the foreign key directly on the child table? Is it just the complexity of knowing what to filter for / how to build the criteria for the selectin query?
In my case I have a parent table with 55,000 rows selected. There are then 323 distinct child records. By joining the parent table it means I end up with stackloads of queries where 1 would do. Is it be possible to have it filter for all the distinct child ids first, and then use those for the IN filter directly on the child table without joining the parent? I guess the normal usage is for it to work in the other direction where the parent is the smaller table and the child has many records? -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
