I've written a custom field (I'm using Django nonrel) for storing
users in a SetField. The SetField doesn't seem to handle serialising
the set of User objects properly, so what I've done is implement the
pre_save method, which returns a set of strings which are the ids in
MongoDB.
The
both on par, as I was hoping/expecting they would be.
The average difference was something like 2 seconds, with the enabled
middleware being the faster one usually. Obviously this means nothing,
and they're both on par and there's nothing to worry about.
On Aug 18, 1:11 pm, Nathan Hoad <
I have a project at the moment that requires a lot of corporate
branding as well as internationalisation/translations etc. Basically
the way the system currently works is that it performs the
translations, then applies branding for specific distributors.
Now we're developing a web-based front end
Hmm, silly me. I posted this to the users group, not the developers
group. My mistake!
On Aug 12, 1:18 pm, Nathan Hoad <nat...@getoffmalawn.com> wrote:
> Hi guys, just wondering what the status is on the official NoSQL
> support? I've done a lot of reading and the last official post
Hi guys, just wondering what the status is on the official NoSQL
support? I've done a lot of reading and the last official post I can
see is Alex Gaynor's GSoC post, from August last year mentioning the
Query refactor and how it should help down the road for NoSQL, but
nothing past that.
owser and proxy
> caching, look into Django's never_cache decorator.
>
> On Jul 16, 9:51 am, Nathan Hoad <nat...@getoffmalawn.com> wrote:
>
>
>
>
>
>
>
> > Hi guys, I migrated my site from PHP to Django about a fortnight ago
> > and everything wen
Hi guys, I migrated my site from PHP to Django about a fortnight ago
and everything went really smoothly, except now there appears to be
some kind of "caching" on certain pages. I say "caching" because I
have no caching enabled in Django, and it seems to be browser based,
i.e. I can open a page in
7 matches
Mail list logo
