After `testFOO` method call test case flushes all data in database. So
if you want to add some logic at this stage - flushing procedure may
take a lot of time and you will get no speed improvements.
On Oct 14, 5:18 am, Simon Litchfield <[EMAIL PROTECTED]> wrote:
> Reloading of fixtures for each t
On Mon, 2008-10-13 at 08:18 -0700, Brian Beck wrote:
> On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote:
> > The only action was three months ago with a DeprecationWarning patch that
> > isn't checked in.
>
> ...and probably shouldn't be, since it still doesn't update the docs.
The fa
Reloading of fixtures for each test gets painful when the fixtures get
big.
Maybe we could continue to have TestCase.fixtures as a list of
'variable' fixtures that do definitely need to be reloaded for each
test... and add a new optional attribute, TestCase.static_fixtures,
which would be a list
On Oct 13, 11:15 am, Brian Beck <[EMAIL PROTECTED]> wrote:
> The only action was three months ago with a DeprecationWarning patch that
> isn't checked in.
...and probably shouldn't be, since it still doesn't update the docs.
--~--~-~--~~~---~--~~
You received this
On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote:
> Secondly this question has been asked, and solved many times. If you search
> through the django-users archives I'm sure you'll find plenty of solutions.
> There are solutions out and about in the blogosphere too.
Actually I think this
Hi,
The auth-decorators to check for permission are nice, but it would
be better, if the authorization could be decoupled from calling the view.
My goal: Check if a user can access a view without calling it, because
I want to disable/hide a link if the user must not call it.
I implemented it in
Thierry,
Firstly django-developers is not the place for this discussion.
Secondly this question has been asked, and solved many times. If you search
through the django-users archives I'm sure you'll find plenty of solutions.
There are solutions out and about in the blogosphere too.
Cheers,
Mik
Hi,
I have a lot of models using this type of fields :
creation = models.DateTimeField(auto_now_add=True)
update = models.DateTimeField(auto_now=True)
But I read that since 2007, it was planned to drop those options from
models.DateField.
Here the post :
http://groups.google.com/grou
