Anyone who mixes the ORM with raw data-modifying SQL concurrently may
well be in for a surprise.
Scenario. Load your model; run your data-modifying SQL; then
explicitly try to reload your model to refresh it's data. Gotcha. The
inbuilt queryset cache will cleverly skip straight over your attempt
> I thought I'd give a quick note so nobody wonders: I'll be on an
> extended vacation April 21 - May 17th. I'll be checking email
> sporadically, but don't really expect anything from me while I'm gone.
> While I'm gone, of course, decisions and work should just go on
> without me -- I can s
Sam, please ask Django usage questions on the django-users mailing
list. This list is for discussion of the development of Django
itself.
But to answer your question, it sounds like you're conflating
"tablespace" with "user schema". What you're wanting to do -- have
the Django user be a user ot
On Sun, Apr 13, 2008 at 6:13 PM, Honza Král <[EMAIL PROTECTED]> wrote:
> > I was going to say "Put the cache into self.foo", but now I'm just
> > realizing that there is just one FormWizard instantiated in urls.py,
> > so different people could be using the same FormWizard instance.
>
> the
On Sun, Apr 13, 2008 at 7:05 AM, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> I was wondering about the reason that middleware classes were used instead
> of decorators to implement middleware functionality. One of the use cases
> that lead me into thinking about it is that I was looking for a way t
If have I understood problem well:
- ibm guys are developers
- community guys are supporters
- developers may NOT look existing code
- developers may look at technical specification
- since django hasn't got specification for writing backend -
developers can't do anything
- supporters may l
On Mon, Apr 14, 2008 at 2:00 PM, James Bennett <[EMAIL PROTECTED]>
wrote:
>
> On Sun, Apr 13, 2008 at 6:05 AM, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> > I was wondering about the reason that middleware classes were used
> instead
> > of decorators to implement middleware functionality.
>
> Ther
On Mon, Apr 14, 2008 at 3:30 AM, James Bennett <[EMAIL PROTECTED]> wrote:
> the useful tricks that a real middleware can do -- for example, you
> can't tweak request.urlconf to change URL resolution, because by the
> time a decorated view comes into play the URL resolution phase is
> over.
We
On Sun, Apr 13, 2008 at 6:05 AM, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> I was wondering about the reason that middleware classes were used instead
> of decorators to implement middleware functionality.
There are two cases, each with drawbacks:
1. Whatever system is available to provide addit
On Sun, Apr 13, 2008 at 6:24 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>
> Hi, Amit!
>
> Check this utils function:
>
> http://code.djangoproject.com/browser/django/trunk/django/utils/decorators.py#L9
This wont really help much as I will still have to apply the decorators
manually to all view
10 matches
Mail list logo
