> On 28 Jul 2015, at 11:31, Jacob Magnusson <[email protected]> wrote: > > I'm trying to avoid "implicit" joins (i.e. more than one entry in the FROM > clause) in my code and I'm wondering if you guys have a good idea on how to > best achieve this. I want to raise an exception if a query changes to have > more than one entry in the FROM clause. An alternative would be to have it > happen only before the query is executed. I'm guessing you would have a good > idea on where to start Michael?
Just chiming in to say I think this would indeed be useful. In my software, I have a few places where queries are built all over the place: column selection here, filters there, and I did at least once have a bug caused by such an "implicit" join. Such bugs tend to be very dangerous, because if the executed query has a DISTINCT clause, they can be invisible, and if the test dataset is small enough they can go undetected. When they land in production with real dataset they cause combinatorial explosions. Regards. -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
