[sqlalchemy] _deep_deannotate and aliased, joined tables

2012-03-30 Thread Christoph Rauch
Hello List, the problem I am facing is that _deep_deannotate, which is used in ColumnProperty.__init__, breaks the FROM clause of my select() object if this select() has a JOIN (either left or right, doesn't matter) as from_obj in it, _where the initial table is aliased_. To illustrate I'll

Re: [sqlalchemy] _deep_deannotate and aliased, joined tables

2012-03-30 Thread Michael Bayer
well the good news is that these cloning bugs, which have the property that each time I spend four hours fixing one I'm absolutely convinced it's the last (a process which began at least four years ago), are my highest priority since there are usually zero workarounds and also indicate there's

Re: [sqlalchemy] _deep_deannotate and aliased, joined tables

2012-03-30 Thread Michael Bayer
really great news, without even any coffee I came up with a patch for this one in less than 30 minutes. I need to create some tests, maybe try to figure out why this hasn't been seen more frequently and something should be committed today. It's on the ticket here:

Re: [sqlalchemy] _deep_deannotate and aliased, joined tables

2012-03-30 Thread Christoph Rauch
Awesome! Thank you very much. :) Am Freitag, 30. März 2012 15:47:44 UTC+2 schrieb Michael Bayer: really great news, without even any coffee I came up with a patch for this one in less than 30 minutes. I need to create some tests, maybe try to figure out why this hasn't been seen more