On 3/30/07, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
> The code is not online (yet). I plan to, but will need to wait for the HP
> acquisition to settle down first...
>
Thanks for your patience with my pestering. :) I know you have
bigger fish to fry just now.
--~--~-~--~~
The code is not online (yet). I plan to, but will need to wait for the
HP acquisition to settle down first...
--Ned.
Jeremy Dunck wrote:
> On 3/30/07, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
>> It wasn't a formal presentation. I was showing Tabblo during the Django
>> app demo session,
On 3/30/07, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
> It wasn't a formal presentation. I was showing Tabblo during the Django
> app demo session, and Adrian noticed that my dev server was spewing more
> info than typical.
Yeah, I figured it was the app demo. I was asking if the middleware
It wasn't a formal presentation. I was showing Tabblo during the Django
app demo session, and Adrian noticed that my dev server was spewing more
info than typical.
--Ned.
Jeremy Dunck wrote:
> On 3/30/07, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>
>> At Pycon, when I showed
>> my tracing m
On 3/30/07, Ned Batchelder <[EMAIL PROTECTED]> wrote:
> At Pycon, when I showed
> my tracing middleware, I got the distinct feeling that its seven new
> settings were a no-no.
I guess I missed that pres. Is it available online somewhere?
--~--~-~--~~~---~--~~
You
Ned Batchelder wrote:
> I think it would be a great idea. I have used similar tracing
> facilities in other (non-Django) projects, and they were invaluable for
> quickly zeroing in on the pathological code that swamped the performance.
>
> I don't know what the feeling of the devs is on clutte
I think it would be a great idea. I have used similar tracing
facilities in other (non-Django) projects, and they were invaluable for
quickly zeroing in on the pathological code that swamped the performance.
I don't know what the feeling of the devs is on cluttering the settings
with individu
In the book "Building Scalable Web Sites", Cal Henderson suggests
putting (possibly abbreviated) app call stacks in SQL comments to
enable logging and performance on the DB backend to be more easily
tied to application paths.
This sounds like a great idea to me.
MySQL, PGSQL and SQLite all supp
