Re: Backwards incompatibility with fancy PostgreSQL queries and QS-RF

I think I posted a similar issue almost simultaneously with Barry here. This affects MySQL 5.0.41 too. See my post: http://groups.google.com/group/django-users/browse_frm/thread/831667d32f01f5d2 On May 1, 5:59 am, Barry Pederson <[EMAIL PROTECTED]> wrote: > On Apr 30, 11:52 pm, "James Bennett"

Re: extra tables subselect issue in QS refactor?

This issue seems to be similar/same as the another post made today http://groups.google.com/group/django-users/browse_thread/thread/ef17cb9fff6d0391 On May 1, 7:44 am, offspinner <[EMAIL PROTECTED]> wrote: > Hi folks, > > I have several rather large SQL queries that I want to

extra tables subselect issue in QS refactor?

Hi folks, I have several rather large SQL queries that I want to return a QS. I need to put a subselect in the tables part of "extra" to achieve this. The example below I can refactor to be more conventional but I have other examples where I need to use this construct. It *seems* since QS refact