On Wed, Feb 25, 2009 at 10:08 PM, smoluf wrote:
> I think there is a way to remedy my complaint without destroying any
> of the current behavior that you outlined (and without sacrificing
> performance).
See, the reason I closed your ticket as wontfix is because I don't
think there is. That is,
> Personally I think this is useful behavior for two reasons:
>
> 1. You get results which, when possible, represent the latest state of
> your database, as opposed to a view into what your database looked
> like back when the query was run.
This is true, but the suggested fix (assign an ar
On Wed, Feb 25, 2009 at 10:04 PM, smoluf wrote:
> If I issue an equivalent query with a QuerySet, however, and then
> select two rows by indexing into the result at two random locations, I
> can not currently be guaranteed that they are different rows because
> the QuerySet will use two different
Hey guys. First I want to apologize for re-opening the ticket, a bit
of a ready-fire-aim moment there. However, I would like to make my
case for the ticket here in a complete way.
I think this is a case of conflating two issues, so I hope I can
separate them and convince you that one of them actu
There are 3 outstanding tickets for FormPreview that add functionality
that exists in FormWizard. Unfortunately, patches for two of them are
backwards-incompatible changes. Both of the backwards-incompatible
tickers are marked "design decision needed", so . . . here I am,
looking for a decision!
oops, wrong group.
sorry, guys.
2009/2/26 Yuri Baburov :
> для багов можно со временем будет перелезть на систему
> http://opentodo.openminds.ru/tasks/
> мне очень понравилась: и дизайном, и функциональностью.
>
> --
> Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov,
> MSN: bu...
для багов можно со временем будет перелезть на систему
http://opentodo.openminds.ru/tasks/
мне очень понравилась: и дизайном, и функциональностью.
--
Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov,
MSN: bu...@live.com
--~--~-~--~~~---~--~~
You r
On Feb 25, 7:24 pm, Nick Craig-Wood wrote:
Sounds like your table and/or innodb/mysql install is broken. It's
hanging on updating statistics. Try REPAIR TABLE or google for
something like "mysql state statistics".
--~--~-~--~~~---~--~~
You received this message be
Following up to myself...
On Wed, Feb 25, 2009 at 09:16:09AM +, Nick Craig-Wood wrote:
> I've finally got to the bottom of why django locks up on our dev server.
>
> Our dev server has mysql query logging turned on with this in
> /etc/mysql/my.cnf
>
> # Query logging
> log=/var/log/mysql/m
I've finally got to the bottom of why django locks up on our dev server.
Our dev server has mysql query logging turned on with this in /etc/mysql/my.cnf
# Query logging
log=/var/log/mysql/mysqld.log
However with that, then simple queries (like looking at the accounts
table in the admin interfac
10 matches
Mail list logo