Russell Keith-Magee wrote:
> Sorry - a point of clarification. the technique I gave you is 1.2
> specific. There's no analog under 1.1, because 1.1. doesn't support
> multiple databases.
That explains a lot; tx.
My current impediment - probably nothing to do with Django - is ...
cursor.
On Tue, Mar 30, 2010 at 12:05 AM, Phlip wrote:
>> qs.query.get_compiler(qs.db).as_sql()
>
> That gives this error message with the usual zero Google hits for that
> error message:
>
> AttributeError: 'BaseQuery' object has no attribute 'get_compiler'
Sorry - a point of clarification. the techniq
> * Similarly, connection.cursor() will only work in the single
> database case. connections[qs.db].cursor()
Aaaand that's not working either. (No connections, no qs.db.)
I must take a break until someone unravels all this, because I don't
know enough about the architecture inside QuerySet...
-
> AttributeError: 'BaseQuery' object has no attribute 'get_compiler'
qs._as_sql() returns a tuple of a SELECT statement, and a (),
presumably with wildcards; I will start there.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
> qs.query.get_compiler(qs.db).as_sql()
That gives this error message with the usual zero Google hits for that
error message:
AttributeError: 'BaseQuery' object has no attribute 'get_compiler'
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
Russell Keith-Magee wrote:
> Interesting idea! Thanks for sharing.
http://www.oreillynet.com/ruby/blog/2008/01/assert_efficient_sql.html
> I've just spent a bunch of time hunting down a performance regression
> that was caused by someone tweaking a database index, so I'd love to
> see something
On Wed, Mar 24, 2010 at 4:56 AM, Phlip wrote:
> Djangoists:
>
> Suppose I want a test to fail if the database would respond to a given
> QuerySet without using my favorite index.
>
> This test case would attempt, at developer test time, to solve the
> same problem as a "soak test" would, at accept
Djangoists:
Suppose I want a test to fail if the database would respond to a given
QuerySet without using my favorite index.
This test case would attempt, at developer test time, to solve the
same problem as a "soak test" would, at acceptance testing time. So
the earlier a test fails - without so
8 matches
Mail list logo