ATOMIC_REQUESTS Alternative - better for highly concurrent systems

Hi, I want to offer something the the community of Django users. If you like the safety net of having each request handled by a transaction, but don't want unnecessary blocking on highly concurrent web applications, then the following may be of interest. The Django transaction documentation of

Django 1.5 cached response has an empty body

With the change to HttpResponse made in Django 1.5, I'm finding that in my code, which caches a generated response, results in an empty body when that page is requested a second time. The first time the page is requested, it is not in the cache, and the page is generated normally and added to th

Re: BigAutoField

omments from Core Developers. > > -- > Pankaj Singh > http://about.me/psjinx > > > On Wed, Jan 23, 2013 at 6:58 PM, SteveB > > wrote: > > Can anybody provide an update on the request to define a BigAutoField in > > Django? > > We could real

BigAutoField

Can anybody provide an update on the request to define a BigAutoField in Django? We could really use this model field type without having to do workarounds and customizations. Can any of the Django developers comment on when this will be released? Thanks, Steve -- You received this message bec

Re: Is Django right for what I am trying to do

Hi Bradley, Just my 2c re feeling comfortable with how django does things:- A high level walkthrough of which bits of Django are used and how they fit together. 1. You define the URL's that you want to present via a web server in urls.py. 2. In the urls.py file you configure url's and map these

Re: Hierarchical data containing different models

Worth a look at django-treebeard as a tree library. I'm doing some work with it at the moment and I'm very impressed with it so far. It's pretty easy to separate the different data and connect to a tree- node object. IMO the api for tree work is good and all of the SQL complexity is hidden. You

Re: Dynamic queryset when instantiating a form with a ModelChoiceField within a formset

which would be passed as a parameter to each form's instantiation. The Django forms.BaseForm.__init__ would have to accept (though would ignore) this argument. Regards, Steve On May 14, 12:45 pm, SteveB wrote: > Hi, > I have a form which has a ModelChoiceField, whose queryset has to

Dynamic queryset when instantiating a form with a ModelChoiceField within a formset

Hi, I have a form which has a ModelChoiceField, whose queryset has to be set dynamically (when the form is instantiated). I have read an earlier posting on how to do this: http://groups.google.com/group/django-users/browse_thread/thread/847ec83e26dd7846/f0b15945a01eafe2?lnk=gst&q=queryset+modelcho

Re: Webservers, Django thread-safeness, etc.

Actually, that statement, "to the best of anyone's knowledge, Django does not have issues running in threaded servers, and if/when bugs are found which contradict that we fix them" is what I was looking for. I probably should have asked, "Is Django intended and designed to be thread safe?" Obvio

Webservers, Django thread-safeness, etc.

Deploying Django behind Apache is great for real web apps, but I also use Django for Desktop apps that employ a web browser as the UI. In this situation, a distribution package that depends on Apache is not an option (too much for end users to manage), and the Django development server's weakness