>
> The intention for 1.3 was to get a class-based view framework in place
> that could serve as a replacement for the existing function-based
> generic views. Since the function-based generics don't have
> permissions, neither does the initial iteration of class-based views.
That's fair enough.
Hi, looking at the new class-based views for 1.3, there doesn't appear
to be an easy way to add row-level permission hooks to the views (as
one can do in ModelAdmin). It seems a strange omission as this should
be quite straightforward and is an extremely common use-case.
For example, if I have a B
I think it depends on requirements; not everything has to be a
reusable app ! For example, if you have a number of interdependent
apps as part of a larger system,and breaking them up makes no sense,
housing them under a single package is good practice.
What you should avoid is using the same name
Try using a) queryset.iterator() to iterate through the results and b)
paginating the results. Otherwise you run the risk of loading all the
results into memory at once,
On Dec 15, 1:44 am, Tracy Reed wrote:
> I have code which looks basically like this:
>
> now = datetime.today()
> beginn
We have been optimizing our server (db and caching) since our recent
launch and one thing we've been looking at is our server status:
Total queries: 4,307,827
Com_admin_commands: 3,754,356
Com_insert: 37,790
Com_select: 1,354,134
Com_set_option: 172,319
Com_update: 52,759
Com_commit: 88,107
(thi
5 matches
Mail list logo
