On Sat, 2007-07-28 at 00:13 -0500, Adrian Holovaty wrote:
> I propose we add a hook to the unit-test framework that would give
> developers access to information about the underlying database queries
> in a given test.
>
> Specifically, I could see (and I currently *have*) needs for the
> followi
On 7/28/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> The whole django.db.connection.queries thing has always been a bit of
> a hack/wart. (Hackwart?) Maybe it's time to expose the underlying
> queries in a more developer-friendly way. Off the top of my head, we
> could allow the registration
On 7/28/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> Specifically, I could see (and I currently *have*) needs for the
> following assertions:
>
> * Assert a given custom model method runs a certain, exact number of SQL
> queries
>
> * Assert a given custom model method's SQL contains a cert
I propose we add a hook to the unit-test framework that would give
developers access to information about the underlying database queries
in a given test.
Specifically, I could see (and I currently *have*) needs for the
following assertions:
* Assert a given custom model method runs a certain, e
